-
Notifications
You must be signed in to change notification settings - Fork 97
✨ Update controller runtime and cluster-api to the newest version (CAPI 1.10) #1628
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
Conversation
…1635) build(tools): make helm and hcloud downloads platform-agnostic Replace hardcoded `linux-amd64` architecture with dynamic `$(go env GOOS)-$(go env GOARCH)` to support multiple platforms and architectures during tool installation. Signed-off-by: Tomas Dabašinskas <tomas.dabasinskas@datolabs.io>
…1637) * 🌱 Add SkipCreatingHetznerSecretInWorkloadCluster to hetznercluster_controller SkipCreatingHetznerSecretInWorkloadCluster indicates whether the Hetzner secret should be created in the workload cluster. By default the secret gets created, so that the ccm (running in the wl-cluster) can use that secret. If you prefer to not reveal the secret in the workload cluster, you can set this to value to false, so that the secret is not created. Be sure to run the ccm outside of the workload cluster in that case, e.g. in the management cluster. Closes #1636
janiskemper
left a comment
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.
I cannot review the changes in the scripts though
I am unsure what you mean. I only see |
|
@cgroschupp thank you for your initial work. The PR is now merged. We will do a new release, when #1647 got merged. |
Based on PR of @cgroschupp 🌱 update controller runtime and cluster-api to newest version by cgroschupp · Pull Request #1623 · syself/cluster-api-provider-hetzner
closes #1662
Changes
Use separate struct for webhooks, and do not export them. Example:
Followed the capi deprecation:
Use docker image of Lychee (do not install it via alpine)
FROM docker.io/lycheeverse/lychee:sha-3592972-alpine@sha256:6609738da2ce125c64658728bd6af93da45852e0744e3335e90c5a5719e080c1 as lychee
CloudInitStatus: Do now hide the underlaying error, when calling
cloud-init statusfailed.There are three cases:
Caller of CloudInitStatus() uses output.ExitStatus() now.
GetCloudInitOutput: Same as for CloudInitStatus: Use output.ExitStatus() to differentiate between error cases.
obtainHardwareDetailsNics: Fail, if no IP was found.
Avoid
&&in shell commands.Related: guettli/bash-strict-mode: Bash Strict Mode
Example:
Was changed to:
BTW, it took some time to understand why
cloud-initwas not installed. The&&made the failingapt-get updatenot terminate the script. Additionally, the error output was swallowed. That was the reason for refactoring to use output.ExitStatus().fix: input.ClusterctlConfigPath is required for DumpAllResources
fix: input.KubeConfigPath is required for DumpAllResources
fix: action "ensure-provisioned" failed: failed to get cloud init output: %!w()' (show real error message now)
updated cilium
Regenerated the cillium and ccm e2e templates
logStatusContinuously():
Show conditions of the wl-clusters.
This is very helpful, as you can see while the e2e test is running, if an error occurs.