Files
velero/site/content/docs/main
Tiger Kaovilai 3a0caba1f5 docs: Clarify that only first loadAffinity array element is used
Addresses #9133 by adding clear documentation about the current limitation
where only the first element in the loadAffinity array is processed.

Changes:
- Added prominent warning at the beginning of loadAffinity section
- Updated misleading examples that showed multiple array elements
- Added warnings to each multi-element example explaining the limitation
- Clarified that the recommended approach is to combine all conditions
  into a single loadAffinity element using both matchLabels and matchExpressions

This provides the "bare minimum" documentation clarification requested
in the issue until a code fix can be implemented.

🤖 Generated with [Claude Code](https://claude.ai/code)

Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>

Apply suggestion from @kaovilai

Signed-off-by: Tiger Kaovilai <passawit.kaovilai@gmail.com>
Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>

Apply suggestion from @kaovilai

Signed-off-by: Tiger Kaovilai <passawit.kaovilai@gmail.com>
Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>

Apply suggestion from @kaovilai

Signed-off-by: Tiger Kaovilai <passawit.kaovilai@gmail.com>
Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>
Co-Authored-By: Claude <noreply@anthropic.com>
2025-08-04 16:28:28 -04:00
..
2025-02-28 08:42:39 +01:00
2025-04-07 09:08:41 -04:00
2022-11-01 18:11:21 +08:00
2022-11-14 19:27:32 +08:00
2023-10-10 13:56:50 +08:00
2023-03-22 14:07:17 +08:00
2024-12-05 14:30:40 +01:00
2025-03-27 14:31:50 +08:00