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

Support kustomize v4 #4975

Closed
estroz opened this issue Jun 9, 2021 · 4 comments · Fixed by #6613
Closed

Support kustomize v4 #4975

estroz opened this issue Jun 9, 2021 · 4 comments · Fixed by #6613
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. language/ansible Issue is related to an Ansible operator project language/go Issue is related to a Go operator project language/helm Issue is related to a Helm operator project lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone

Comments

@estroz
Copy link
Member

estroz commented Jun 9, 2021

Feature Request

Describe the problem you need a feature to resolve.

kustomize v4.0.0 was released recently. Most operator-sdk usage is compatible, but certain components are not (see #4597).

Describe the solution you'd like.

Permit both v3 and v4 kustomize binaries to work with all operator-sdk projects going forward.

/language go
/language ansible
/language helm
/kind feature

@openshift-ci openshift-ci bot added language/go Issue is related to a Go operator project language/ansible Issue is related to an Ansible operator project language/helm Issue is related to a Helm operator project kind/feature Categorizes issue or PR as related to a new feature. labels Jun 9, 2021
@estroz
Copy link
Member Author

estroz commented Jun 9, 2021

This may require kubebuilder changes for Go operator projects.

@estroz estroz added this to the Backlog milestone Jun 9, 2021
@estroz estroz removed this from the Backlog milestone Jun 9, 2021
@jberkhahn jberkhahn added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 14, 2021
@asmacdo asmacdo removed the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 21, 2021
@asmacdo asmacdo added this to the Backlog milestone Jun 21, 2021
@asmacdo asmacdo added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Jun 21, 2021
@estroz
Copy link
Member Author

estroz commented Jun 21, 2021

Ping me for more info if assigned.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 19, 2021
@fabianvf
Copy link
Member

/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. language/ansible Issue is related to an Ansible operator project language/go Issue is related to a Go operator project language/helm Issue is related to a Helm operator project lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants