Search for a command to run...
Well, I worked as:
No comments yet. Be the first to comment.
Some stories about me, k8s and my journey to elk on k8s for my weather dashboard.
Introduction True, my hate/love relationship with k8s is still going on, but I've to say, that all in all you can learn a lot, even if you don't use the know-how daily at work. For me, it gives me an understanding of what my developers and ops people...
Revisiting my Top 5 project ideas from May 2022 and my next Top 5 before Summer hiatus
Over my last three posts, I have shared some of my k8s anecdotes, detailing my experiences surviving since last Christmas. In this concluding entry of my adventure series, I aim to bring closure to this chapter of my k8s journey. Within this blog pos...
Introduction True, my hate/love relationship with k8s is still going on, but I've to say, that all in all you can learn a lot, even if you don't use the know-how daily at work. For me, it gives me an understanding of what my developers and ops people...
... In the last part, you could read about the beginning of my k8s journey. The rescue of my Monitor Raspberry Pi, and the build of my 5 Raspberry Pi k8s cluster. Also the basic setup with DietPi OS. In part II, I want to show how I did the k8s setup...
So, a new year, and a lot of time to continue some adventures over the Xmas holiday break. After the usual visit to my family's place, I came home and was surprised with a broken k8s cluster. So I thought. But after some investigation, I found out, t...
... when it comes to configuration apps. Don't get me wrong, I actually like the concept behind containerization and Kubernetes. When I first saw docker and learned about the concept of containers, I knew instantly that this is the future, especially cause I worked already for 2 years with virtualization.
Ok, probably I did not foresee the full extent how containerization is used today, but I knew that it will revolutionize software development and software testing. So naturally I jumped the boat and started my container journey with docker.
Back then I found docker configuration not so easy, but I could figure it out and soon I had my own docker host and my first images up and running in my Home Lab. Man, was I proud. Over the years I continued my journey, only to learn, that companies in Germany where back in 2015/2016 very hesitant and reluctant to adopt this new technology.
Once in a while I discovered a company where docker or better container were a raising star, but it was not mainstream, yet. So it was hard for me to score contracts with my docker know how. Well, when you are a free lancer, you sometimes have to take jobs, so money is coming in and you can your bills. That's how I lost focus on docker (and docker swarm) and the upcoming Kubernetes evolution.
When I got in touch with containers again in 2019, so much had changed. Docker is still a player, but Kubernetes has won the container wars, if there was one. Very fast I learned, with my old docker know how, I'm no longer able to compete in the DevOps market, since every serious company now a days uses Kubernetes on premise or in Azure, Google or AWS. Rarely they use docker desktop for software development. And I simply knew I had to learn Kubernetes and everything you need to know about it.
I did what I always do and begun to try to install Kubernetes on my Home Lab. Well, not much to say, I failed. As far as I remember, Kubernetes to install in 2019 was still a complicated task. At least for me. But lucky for me I scored a job at a company who used docker, docker swarm and Kubernetes quite extensively. And they wanted to migrate all docker related applications to Kubernetes. What an opportunity for me.
The department lead even convinced the upper management to abandon docker, which they introduced about 1,5h earlier and move to Kubernetes and to a SUSE based Kubernetes cluster in their on-premise data centers. So I was naturally happy to get involved in that. Cause I still could use my docker know how, and slowly could build up my Kubernetes know how. But fate struck again. I and the company soon realized, that I was not made for Kubernetes. I simply could not get my head around the - in my eyes - complicated configuration model of Kubernetes. And what made everything worse, a fellow free lancer, who also worked in this department, was 20years younger and an expert in Kubernetes configurations and helm charts. So I and this company parted ways, and I was still laking Kubernetes know how.
Again, I did smaller jobs as "old fashioned" DevOps engineer and Scrum Master. When I scored another job, where at least docker and maybe Kubernetes was on the horizon. But then this little dangerous virus hit the world and everything changed again. Budgets where cut, projects where canceled. You had to get the jobs you can get. And again, no luck with Kubernetes.
But the lockdown and the extensive Home Office gave me the chance to put my Christmas gift, a raspberry pi 4B 8GB, from 2020 to a good use and try a Kubernetes install, again. And since my first try in 2019 the technology how to install Kubernetes changed a lot, to the better I must say.
So here I am in July of 2020, I have my Pi equipped with a ssd, have a k3os running with a k3s cluster, and I have my ELK stack up, and running - actually I managed to accomplish it, today - and can finally say, I have my first real experience with my own little Kubernetes cluster in my Home Lab.
But let me tell you, how hard that was for me. And that's why I chose this title for my little story. It was a pain, but I will share this story a different time.
As always apply this rule: "Questions, feel free to ask. If you have ideas or find errors, mistakes, problems or other things which bother or enjoy you, use your common sense and be a self-reliant human being."
Have a good one. Alex
