-
Notifications
You must be signed in to change notification settings - Fork 78
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
Resolve kustomize warnings #1752
Resolve kustomize warnings #1752
Conversation
bases are deprecated and should be replaced by resources. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
it should be safe to replace patchesJson6902 with patches now. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
no changes just removing empty indentation. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
the "kustomize edit fix" complains about these missing. Signed-off-by: Lukáš Doktor <ldoktor@redhat.com>
76c098e
to
429b4b7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ldoktor !
We had some issues in the past that some of our code wasn't compatible with the new kustomize format, so a couple of us made this change before and had to back it out (e.g. #1023), but maybe we have bumped versions enough for it to work now as the libvirt e2e tests are passing? I'll try and test it out with ibmcloud today to see if that shows any issues... |
It looks to work on IBM Cloud so far, but I'm still hitting kustomize warnings:
May switching those were the blocking issues we had before? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there are some other warnings still kicking around, but it's still an improvement to remove these. Thanks @ldoktor!
While setting-up my libvirt+kcli I noticed a few warnings from kustomize. I used
kustomize edit fix
to learn what to replace and then addressed all places usingsed
. Note the behaviour should not change but I have only tested the default libvirt e2e setup with kcli.