Thoughts on DevOps, cloud-native technologies, and platform engineering.
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.
As I’m using Scaleway more and more for my Cloud hosting needs I wanted to move my personal blog which I hosted on AWS (S3/Cloudfront) to Scaleway. Since there is no CDN alternative on Scaleway (yet) I needed an other alternative and choose Cloudflare as they have a generous free tier and are being used by some bigger companies which means they have mature infrastructure and services
Read more
In this example we will show how you can deploy a serverless application written in Golang and deploy it in multiple regions using the AWS CDK with Python as the configuration language.
Read more
As serverless is being used more and more to build ‘real’ applications and not only used to execute small tasks, the need for monitoring becomes even more important. However, when using a serverless architecture most of the tools and practices we used when working with servers and containers are not applicable anymore.
Read more