-
Notifications
You must be signed in to change notification settings - Fork 928
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 the remaining Kustomize 5 warnings #2991
Comments
/assign |
@juliusvonkohout i'd like to help. |
You can just start creating PRs. For the common components usually within kubeflow/manifests (there i can merge them fast for you so best start there) and for most things under "apps" in the specific working group repositories, e.g. kubeflow/pipelines. We then synchronize them back with the scripts in /hack. And of course multiple contributors can work on this task in parallel and create PRs. |
@mahdikhashan thank you and congratulations to the merged PR for kserve-models-web-application |
Shall we reopen this issue for other components? |
yes |
You can also continue in parallel with other components if some PRs are blocked by review. |
@juliusvonkohout @mahdikhashan everything under |
|
@juliusvonkohout For each |
You can run kustomize build and check where the warnings come from. If there is a warning you can run kustomize edit fix. But maybe you need manual changes as well such that diff -u is zero. Furthermore for all paths containing "upstream" you also have to raise a PR in the respective upstream repository. |
/assign |
@milinddethe15 it's a big task so let's divide amongst ourselves.. let us know which directories are you are currently working on so that we can cut down on duplication of effort. |
@vikas-saxena02 Thank you, I can do for top two starting directories: @juliusvonkohout Are we using |
/unassign |
We are on 5.4 but I think you can test with 5.6 as well. The best thing is to prioritise the things from /example/kustomization.yaml |
as per readme version 5.2.1+ can be used ![]() |
We currently use 5.4 in our cicd |
You can just start creating PRs. For the common components usually within kubeflow/manifests (there i can merge them fast for you so best start there) and for most things under "apps" in the specific working group repositories, e.g. kubeflow/pipelines. We then synchronize them back with the scripts in /hack.
And of course multiple contributors can work on this task in parallel and create PRs.
Version
master
Detailed Description
Steps to Reproduce
kustomize build example.
see also kubeflow/katib#2511
You need to fix many of then in the appropiate upstream repository, not in our synchronizes upstream folders.
Screenshots or Videos (Optional)
No response
The text was updated successfully, but these errors were encountered: