I have been deploying containers and creating applications on Kubernetes for the better part of the last couple of years. I should have written a lot more about the journey because there is so much to learn (by doing quite a few mistakes).
I should have learned by now that any of these great new ways of doing things that will simplify the delivery of applications is a journey where you are going to re-learn how to do what you have always been doing. The same “problems” exist in creating an application no matter the framework or language.
The new tool is going to address pain points from the last best framework ever and it will be very attractive to use the new one. The fun is in solving all the other problems that still exist and have not necessarily been addressed as well as the pain points that attracted you to it.
I had to re-learn so much about networking with Kubernetes because your micro-services all need to communicate with each other.
I had to learn a lot about Kafka because it is our messaging queue. Please don’t tell them that is what it is. It is so much more.
I had to learn about service mesh and got to the points of many memes about this one.
We had to learn so much about so many different applications and infrastructure pieces that the promise of delivering faster is not as true as we would have liked. Don’t get me wrong, I love learning but I hate over-promising and finding myself in a bad position.
The journey is far from done and I have an awesome team that is helping me and I hope that I am helping them along the way as well.
May the learning continue…
I have been getting an error every time I try to install a new homebrew package and I found a quick and easy solution to it.
The problem looks like this:
user1$ brew install kubernetes-helm
Warning: git 2.15.1 is already installed
Error: Git must be installed and in your PATH!
Error: The following formula:
cannot be installed as a binary package and must be built from source.
Install the Command Line Tools:
Git is available on my system without issues so I was puzzled about this “invalid” error.
I found that if you set this variable:
It would allow brew to update and then install new packages without an issue.
Very simple workaround.
I was not suppose to go this year because it was the turn for a co-worker but since that person left us for greener pastures I was lucky to be the next in line.
I was quite happy to be going.
I did not really remember why I wanted to be there until I was there for a few hours. Yes I wanted to go to many of the technical sessions and my agenda was made before the event started. I am always impressed that the presenters are the people doing the code or in charge of the technical team responsible for what is being presented. The presenter can answer many of the questions and if they can’t most of the time the rest of their team are in the audience. The quality of these presentations are great because of this involvement.
But as much as the technical sessions are great it was Jeremy from trendhunter.com that reminded me why I loved the Summit so much. It is about the culture.
The culture at the Summit and at Red Hat is very different than what I see where I work. The collaboration with everyone is the norm in the open source communities and Red Hat certainly makes it a point to always act in collaboration.
That different mentality is good shock and certainly allowed me to see others thinking differently but also to wake me up. When you are challenged in how you execute your job you can better evaluate the reasons you do it that way. You can also see what you can change.
In my case it is a little more than that. I am uncomfortable in how we approach our execution of what we need to do. I am a lot more interested in the collaboration model that I have seen during the Summit. In that regard I think that I need to challenge a lot more than just myself. Is it just the greener pasture syndrome, I don’t know. I think that I will have to wait a month and re-evaluate what I have seen and how I feel about it.
I think that the most important sentence from this Summit will be “culture over strategy”.