Skip to content
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

Plans to upgrade to Kustomize v5.5 #1299

Closed
mdraevich opened this issue Dec 5, 2024 · 3 comments · Fixed by #1304
Closed

Plans to upgrade to Kustomize v5.5 #1299

mdraevich opened this issue Dec 5, 2024 · 3 comments · Fixed by #1304

Comments

@mdraevich
Copy link

Good day!
First of all, thank you for maintaining and developing the project 🙌.

Could I ask you about the plans for updating Kustomize to v5.5.0?
If possible, we would like to know which kustomize-controller version we should expect and its planned release date.

Our team has encountered a critical issue with Kustomize Controller and Crossplane (kafka-provider). This issue is resolved in this particular version (bug fix: Add Annotation to Control Inline List Conversion in Kustomize Resources).

Thanks in advance,
Have a great day!

@stefanprodan
Copy link
Member

Today I've merged Kustomize v5.5.0 into Flux shared packages fluxcd/pkg#828

The next Flux minor release will include this update, but this can't happen earlier than February 2025.

@stefanprodan
Copy link
Member

@mdraevich I've published a release candidate of kustomize-controller that contains the Kustomize 5.5 update. You use these images until Flux 2.5 is released:

  • ghcr.io/fluxcd/kustomize-controller:rc-9974a49b
  • docker.io/fluxcd/kustomize-controller:rc-9974a49b

@mdraevich
Copy link
Author

mdraevich commented Dec 6, 2024

@stefanprodan

Thank you for providing the information — it was truly helpful!
The release candidate is fantastic news, as we can now proceed with testing.

Thanks once again, have a great day!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants