-
Notifications
You must be signed in to change notification settings - Fork 287
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
Bump kustomize to v5 #2886
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
chrischdi
added
the
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
label
Apr 8, 2024
k8s-ci-robot
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Apr 8, 2024
cc @adityabhatia If you want to / have time |
Hey @sbueringer and @chrischdi, I'm interested. |
Sure. Feel free to go ahead! /assign @prashantrewar |
Hey @sbueringer, Could you please guide me on this issue. I am new to this project. Thank you |
PTAL at: kubernetes-sigs/cluster-api#10294 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
/kind feature
Describe the solution you'd like
CAPI recently bumped kustomize to v5:
We should do the same for CAPV and all kustomize templates we have.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: