-
Notifications
You must be signed in to change notification settings - Fork 616
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
Update Flux controllers to Kustomize v5.2 #3991
Comments
this should be unblocked by the release of Kubernetes v1.28.0 |
Kubernetes 1.28.0 is just one of many Flux dependencies that must move to Waiting on:
After cli-utils has been migrated to gnostic-models, we need to reach to Cosign to do the switch. |
Hi, where are we with this issue ? It seems that #3284 may be link to this one as we would need to update to kubernetes 1.28. |
We decided to hard fork We'll ship Kustomize v5.2 with Flux v2.2.0. |
We should update Flux from Kustomize v5.0.3 to v5.2.1 which comes with a major breaking change: Kustomize components are now applied after generators.
TODOs
Use
kustomize/api@v0.15.0
andkustomize/kyaml@v0.15.0
in:Blockers
ℹ️ Fixed by hard forking Kubernetes cli-utils under https://github.com/fluxcd/cli-utils
As with every Kustomize API minor release, we can't upgrade right away. This time, the issue is that Kustomize has switched to
google/gnostic-models
while Kubernetes and controller-runtime are usinggoogle/gnostic
, which are incompatible and make Flux panic:Before we can update Kustomize, we need to wait for all our dependencies: Kubernetes, controller-runtime, Helm, Cosign, etc, to replace the usage of
google/gnostic
withgoogle/gnostic-models
. This will probably take many months 😢Refs:
The text was updated successfully, but these errors were encountered: