Skip to content

Conversation

@cmorinupgrade
Copy link

Summary

Removes the deprecated preserveUnknownFields field from all argo-rollouts CRDs. This field has been deprecated in Kubernetes API and should be removed from CRD specifications.

Details

The preserveUnknownFields field at the CRD spec level was deprecated in favor of the more granular x-kubernetes-preserve-unknown-fields field within OpenAPI schemas. This change:

  • Removes preserveUnknownFields: false from all 5 argo-rollouts CRDs
  • The modern x-kubernetes-preserve-unknown-fields field is already correctly placed in the OpenAPI schema definitions where needed
  • No functional changes to CRD behavior

Affected CRDs

  • rollout-crd.yaml
  • analysis-run-crd.yaml
  • analysis-template-crd.yaml
  • cluster-analysis-template-crd.yaml
  • experiment-crd.yaml

Testing

The CRDs maintain their existing validation behavior as x-kubernetes-preserve-unknown-fields is already properly set in the schema definitions.

Checklist

  • Chart version bumped (2.40.5 -> 2.40.6)
  • Changelog added to Chart.yaml annotations
  • Follows conventional commits format
  • Single chart modification (argo-rollouts only)

…m CRDs

The preserveUnknownFields field at the CRD spec level has been deprecated
in Kubernetes and should be removed. The modern x-kubernetes-preserve-unknown-fields
field is already present in the OpenAPI schema definitions where needed.

This change removes the deprecated field from all 5 argo-rollouts CRDs:
- rollout-crd.yaml
- analysis-run-crd.yaml
- analysis-template-crd.yaml
- cluster-analysis-template-crd.yaml
- experiment-crd.yaml
@yu-croco
Copy link
Collaborator

Thank you for your PR. Some people made the same PRs and we've been waiting for upstream to release it since we follow upstream's manifest.

@yu-croco yu-croco added the awaiting-upstream Is waiting for a change upstream to be completed before it can be merged. label Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

argo-rollouts awaiting-upstream Is waiting for a change upstream to be completed before it can be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants