Nuage: Back to Basics
In my last post, I discussed how I was spending the majority of my non-work programming time focusing on Kubernetes contributions, with a particular focus on sig/node. Well, that statement is still true :) Hopefully, I’ll find the time in 2020 to blog more regularly about this work, but it’s not what I’m going to share today.
Introducing Nuage
Rather, I’m excited to post today about Nuage. Nuage is the name I’ve given to my project to manage all aspects of my personal computing in the cloud.
Nuage’s main goal is enabling understanding, and controlling, of every aspect of my personal cloud computing. This goal is in reaction to a tension I felt with my old Kubernetes cluster, which I managed via Kops. Ultimately, I didn’t feel I had the level of understanding or control to feel as if I was truly owning my self-hosted cluster. I was relying too much on “magic” from Kops and also feeling restricted by some of the imposed limitations (specifically the version of k8s I could run).
So what?
So what exactly does the introduction of Nuage mean?
First, I’ve deprecated my personal-k8s project and torn down my Kubernetes cluster.
Second, and as a direct result, this blog is now deployed via Terraform code defined in Nuage. The actual host, based on an AMI baked via Packer, is a simple nginx host serving the blog as a static site.
Don’t worry, I’m not done with self-hosting Kubernetes :) I just have a new plan for how I want to deploy/manage my personal cluster. At a high level, my plan is to use kubeadm, in conjunction with Packer/Terraform, to manage my Kubernetes cluster with finer-grained control. This new method is still in the very early phrases, and progress may be slow because contributing code to the actual Kubernetes project remains my main focus. Still, I’m very excited :)
Conclusion
Now y’all are up to date with my plans for self-hosting :) I’m looking forward to lots of programming in 2020 and hope I have some exciting projects to share!