There is an unordered list of volumes in the falco scc yaml in the falco helm chart. After deployment, the kube-api orders this list alphabetically. However, other tools, such as ArgoCD just compare plain yaml while verifying the resource during runtime. This is prone to error and may mark the application as invalid which is of course a false positive. Ordering the volumes alphabetically in advance would mitigate the problem, making it more robust in many usecases.
How to reproduce it
deploy the falco helm chart via ArgoCD. The application should be unable to sync as Argo just compares plain yaml.
Describe the bug
There is an unordered list of volumes in the falco scc yaml in the falco helm chart. After deployment, the kube-api orders this list alphabetically. However, other tools, such as ArgoCD just compare plain yaml while verifying the resource during runtime. This is prone to error and may mark the application as invalid which is of course a false positive. Ordering the volumes alphabetically in advance would mitigate the problem, making it more robust in many usecases.
How to reproduce it
deploy the falco helm chart via ArgoCD. The application should be unable to sync as Argo just compares plain yaml.
Expected behaviour
Everything should have synced properly
Screenshots