Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(argo-rollouts): Removed preserveUnknownFields from the CRD(s) whi… #923

Closed
wants to merge 1 commit into from

Conversation

flaviolemos78
Copy link
Contributor

@flaviolemos78 flaviolemos78 commented Sep 6, 2021

Removed preserveUnknownFields from the CRD(s) which is disallowed on the v1 API (https://kubernetes.io/docs/reference/using-api/deprecation-guide/#customresourcedefinition-v122)

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • I have bumped the chart version according to versioning
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.
  • My build is green (troubleshooting builds).

Changes are automatically published when merged to master. They are not published on branches.

…ch is disallowed on the v1 API

Signed-off-by: Flavio Lemos <[email protected]>
@mkilchhofer
Copy link
Member

I'd keep this as long as the upstream project (our sibling project) uses this: https://github.com/argoproj/argo-rollouts/tree/v1.0.2/manifests/crds

Can you open an issue or PR over there?

@flaviolemos78
Copy link
Contributor Author

I'd keep this as long as the upstream project (our sibling project) uses this: https://github.com/argoproj/argo-rollouts/tree/v1.0.2/manifests/crds

Can you open an issue or PR over there?

Created PR on the upstream project to ensure consistency: argoproj/argo-rollouts#1524

@flaviolemos78
Copy link
Contributor Author

Upstream project is keeping the property to allow smooth transitions between v1beta into v1 api versions. Eventually it will be removed. Closing this PR until upstream deletes the property

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants