Argo Workflows: CRDs do not preserve unknown fields anymore #3129
Labels
argo-workflows
awaiting-upstream
Is waiting for a change upstream to be completed before it can be merged.
bug
Something isn't working
Describe the bug
The update of argo workflows here to v3.6.0 (#3037) also updated the CRDs. Unfortunately this causes issues, e.g. for values in the
wfeb.spec.submit.metadata
section (argo-helm/charts/argo-workflows/templates/crds/argoproj.io_workfloweventbindings.yaml
Lines 669 to 670 in 27ef4ec
argo-helm/charts/argo-workflows/templates/crds/argoproj.io_workfloweventbindings.yaml
Line 37 in 5a57de4
"Upstream" this has been fixed a few days ago by adding the missing fields in the CRDs: argoproj/argo-workflows#14044
Instead of awaiting the next release, I'd like to propose to only update the CRDs to the fixed versions. In case noone objects, I'll prepare a PR tomorrow (CET).
Related helm chart
argo-workflows
Helm chart version
0.45.x
To Reproduce
Apply the following manifest:
Let k8s complain:
Expected behavior
WorkflowEventBinding is accepted by k8s api.
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: