Hello! This is the Stateful edition of Kubelist. So called because the resources below can help you get started on your stateful journey or help you expand your mind on how you might think about incorporating state into your Kubernetes app (AWS service broker! gVisor! Digital Ocean primitives!) .
Bonus: Obsessed with hot reloading all the codes? Check out ways to incorporate that into your dev workflow in a Kubernetes blog post below. 🎉
A good basic overview of how and why you might consider DaemonSets and StatefulSets for managing stateful services in Kubernetes. The post doesn’t mention how Stateful services in Kubernetes deal with taints, tolerations, or antiaffinity on nodes.
If you are a digital ocean fan (we all have our preferred cloud providers), now you can use their managed Kubernetes that takes advantage of the Digital Ocean cloud primitives that you know and love. Check out early the access signup here.
Google is continuing its container security efforts. This one is really cool. A container runtime that runs containers unprivileged and provides a more secure and trusted layer of access to your systems kernel. Now that I can get into.
An operator is a service you build for managing your kubernetes application. This is particular useful for stateful applications because, for instance, a postgres operator can do backups based on all kinds of conditions that represent how your operators would have done backups The operator sdk is now open source! For more on operators check this page.
Did you know you can do hot reloading with Kubernetes? Ksync looks particularly interesting! Take a look at this sweet post on boosting your Kubernetes development workflow.
P.s. they included walkthroughs on some of the tools they discuss!
You can provision AWS services (well, some) through Kubernetes? Sounds cool! It seems to be quite a bit of overhead to manage (a la IAM policies and set up with Kops).
Wondering if AWS Kubernetes Engine will have a managed service catalog and service instance plugin all set up already so you can just write your YAML and be done with it?
Notice how it says 3,300 Users...