-
Notifications
You must be signed in to change notification settings - Fork 20
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
Release rancher-turtles 0.2.0+up0.11.0 #150
Conversation
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.
LGTM
Setting this back to draft as @Danil-Grigorev pointed out that the repository override we used via clusterctl isn't working via the CAPI operator:
I will try to find a different approach via the providers section |
The scenario with repository |
3f749df
to
8fce721
Compare
The current clusterctl override is not working ref this fix: kubernetes-sigs/cluster-api-operator#598
ad12f48
to
2132d0b
Compare
Also include a variable and configuration to override the ipam controller image
2132d0b
to
567d666
Compare
Ok this is now working with all images overridden to the OBS ones:
@alknopfler and @Danil-Grigorev please could you take another look and check if you're happy with this revision? Thanks! |
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.
This looks good to me, just a comment - the original issue should be fixed and we are planning to release it soon.
- condition: cluster-api-operator.enabled | ||
name: cluster-api-operator | ||
repository: file://./charts/cluster-api-operator | ||
version: 0.12.0 |
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.
We have released operator version with the fix for images
section of clusterctl.yaml, so it can be used as well.
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 a lot for working on that - we can pick up that in our next rebase which should simplify the configuration 👍
Continuation of the work discussed via suse-edge#6 Depends on suse-edge/charts#150
This aligns with the recently added suse-edge charts which enable management of CAPI dependencies via Rancher Turtles Depends On: suse-edge/charts#150 (merged) suse-edge/charts#154
Continuation of the work discussed via suse-edge#6 Depends on suse-edge/charts#150
Continuation of the work discussed via #6 Depends on suse-edge/charts#150
This rebases to the latest 0.11.0 turtles release, and also rebases the versions of Core CAPI, CAPM3 and the RKE2 provider.
Note that to enable this to install reliably via EIB we currently need a workaround for rancher/turtles#627 until a version with rancher/turtles#705 is released, passing a values file like this should work:
It's then also necessary to pass a manifest as follows since the chart pre-install hook is no longer taking care of this.