Conversation
Signed-off-by: Gustavo Carvalho <gustavo@externalsecrets.com>
|
|
Heyy @gusfcarvalho 👋 is this incompatible with versions of k8s < 1.30? ( Not sure if its a k8s problem anyway ) We run
|
|
Also incompatible with at least Kind k8s 1.30 - 1.32. I use the ESO bundle in CI pipelines to verify that the chart is installable, and the change has broken all of them. I've verified with Kind versions 1.29 - 1.32. |
|
This most likely isn't a k8s version problem per say. I'll take a look at what's up. |
|
Thank you @Skarlso ! |
|
Removed the hook completely. I'll test this out see if it works. #4675 |
|
Please try the pull request. I tried and it seems to be okay since conversion is an optional field. |
@Skarlso are the changes merged? Its still the same issue right now!! Can you please confirm this once? TY for understanding! |
|
No, it's only on a branch for now. It's not merged yet. |



when users specify
kubectl apply -f, they need to havespec.conversion: {}explicitly. While, with ahelm upgrade, they need to have noconversionset for helm to upgrade the manifest.With helm, the error is:
While with kubectl apply (regardless if server side or client side), the error is:
I think this covers most of the ways people would apply this patch, so the proposal here is to fix the bundle so that
kubectl applyworks, and opt out (we already did) helm charts from it.I also did a lot of fixes to Makefile now that I am using
nerdctlinstead ofdocker