Flux CD
Medium
Concepts
In Flux 2.10, what happens to spec.summary when a v1beta3 Alert is converted to notification.toolkit.fluxcd.io/v1?
Select your answer:
Show answer and explanation
Answer: It is dropped, and eventMetadata.summary replaces it
Explanation
The v1 Alert has no summary field, so converting a v1beta3 Alert drops it without an error. To keep the summary line in notifications, set it under spec.eventMetadata.summary. flux migrate -f warns about each removed field and names its replacement.
More medium Flux CD questions
- In Flux 2.10, how can a HelmRelease install an OCI chart without a separately declared source object?
- A Kustomization must only be applied after another Kustomization that installs CRDs is ready. Which field do you set?
- What does spec.wait: true do on a Flux Kustomization?
- How do you substitute a per-cluster value such as ${cluster_region} into the manifests a Flux Kustomization applies?
- How does Flux decrypt Secrets that are stored encrypted with SOPS in Git?
- What does the --no-cross-namespace-refs=true flag on the Flux controllers do?