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

(ansible/v1, helm/v1): deprecate the flag since APIs is not longer offered from k8s 1.22 and this flag is deprecated for Golang #5815

Merged
merged 2 commits into from
Jun 8, 2022

Conversation

camilamacedo86
Copy link
Contributor

Description

deprecate the flag since APIs is not longer offered from k8s 1.22 and this flag is deprecated for Golang

NOTE: Users should no longer be using this option since if they scaffold projects with v1beta1 it will no longer work on Kubernetes versions >= 1.22. By using v1 for CRDs they can create projects which can work since Kubernetes 1.16

@camilamacedo86 camilamacedo86 requested a review from asmacdo May 29, 2022 10:31
@openshift-ci openshift-ci bot requested a review from jmrodri May 29, 2022 10:31
@camilamacedo86 camilamacedo86 requested review from varshaprasad96 and fabianvf and removed request for jmrodri May 29, 2022 10:31
…fered from k8s 1.22 and this flag is deprecated for Golang

Signed-off-by: Camila Macedo <[email protected]>
Copy link
Contributor

@everettraven everettraven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one nit on the warning wording.

internal/plugins/util/message.go Outdated Show resolved Hide resolved
entries:
- description: >
For Ansible/Helm based-operators (ansible/v1, helm/v1), deprecate the flag `crd-version` since
`v1beta1` APIs is not longer offered from k8s 1.22 and this flag is deprecated for Golang.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to back port this to the SDK release which supports k8s 1.22?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not a bug fix so if we not be able to backport that is 100% fine.
However, I think that would be cool if we are able to do that

Copy link
Member

@laxmikantbpandhare laxmikantbpandhare left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 7, 2022
Copy link
Member

@jmrodri jmrodri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@camilamacedo86 camilamacedo86 dismissed everettraven’s stale review June 8, 2022 15:08

all suggestions were addressed

@camilamacedo86 camilamacedo86 merged commit 6eb41e8 into operator-framework:master Jun 8, 2022
@camilamacedo86 camilamacedo86 deleted the v1beta1 branch June 8, 2022 15:09
VenkatRamaraju pushed a commit to VenkatRamaraju/operator-sdk that referenced this pull request Jun 9, 2022
…fered from k8s 1.22 and this flag is deprecated for Golang (operator-framework#5815)

* (ansible/v1, helm/v1): deprecate the flag  since  APIs is not longer offered from k8s 1.22 and this flag is deprecated for Golang

Signed-off-by: Camila Macedo <[email protected]>

* Update internal/plugins/util/message.go

Co-authored-by: Bryce Palmer <[email protected]>

Co-authored-by: Bryce Palmer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants