We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Flatcar is currently running the version 5.2.0 while the 5.4.2 is out and soon a new release should bring the following patch: coreos/afterburn#931 which is required for CAPO (Cluster API OpenStack) project (kubernetes-sigs/cluster-api-provider-openstack#1564)
cargo-ebuild
Have a look to the afterburn changelog (coreos/afterburn@v5.2.0...v5.4.2)
EDIT: Discussed with @mdbooth during CAPO office hours: "what would be the best way to have the upgrade into Flatcar" - I see two options:
Here's the CAPO PR: kubernetes-sigs/cluster-api-provider-openstack#1564
The text was updated successfully, but these errors were encountered:
+1 for the 2nd option, "backport it to Alpha / Beta only and change the Flatcar image to Beta for the CAPO CI".
Sorry, something went wrong.
Aftberburn 5.5.0 is out: https://github.com/coreos/afterburn/releases/tag/v5.5.0
dongsupark
Successfully merging a pull request may close this issue.
Current situation
Flatcar is currently running the version 5.2.0 while the 5.4.2 is out and soon a new release should bring the following patch: coreos/afterburn#931 which is required for CAPO (Cluster API OpenStack) project (kubernetes-sigs/cluster-api-provider-openstack#1564)
Implementation options
cargo-ebuild
the new dependencies listAdditional information
Have a look to the afterburn changelog (coreos/afterburn@v5.2.0...v5.4.2)
EDIT: Discussed with @mdbooth during CAPO office hours: "what would be the best way to have the upgrade into Flatcar" - I see two options:
Here's the CAPO PR: kubernetes-sigs/cluster-api-provider-openstack#1564
The text was updated successfully, but these errors were encountered: