Static websites have always been simple to deploy - until you try to do it “the Kubernetes way.” Traditional approaches involve init containers copying files, persistent volumes, or baking content into web server images. Each has drawbacks: complexity, storage dependencies, or rebuilding entire server images for content changes.
Read more
This first appeared on autops.eu
When updating the Kubernetes version of a Talos cluster from version 1.32.x -> 1.33.0 I ran into the following situation where the install would stop.
$ talosctl --nodes <<talos node>> upgrade-k8s --to 1.33.0
automatically detected the lowest Kubernetes version 1.32.0
discovered controlplane nodes ["10.0.0.3"]
discovered worker nodes ["10.0.0.4" "10.0.0.2"]
checking for removed Kubernetes component flags
checking for removed Kubernetes API resource versions
NODE COMPONENT REMOVED FLAG
10.0.0.3 kube-apiserver cloud-provider
10.0.0.3 kube-controller-manager cloud-provider
Kubernetes v1.33 removes the --cloud-provider flag from core components
(kube-apiserver, kube-controller-manager). If you’re using an external
cloud controller manager (CCM), you need to remove this flag from your
configuration before upgrading. Your CCM will continue to work - it doesn’t
depend on these flags anymore.