This post is part of accelerated learning project, Outpacing the fast-paced world.
A friend of mine suggested me to contribute to Kubernetes as part of achievingmy goal. i liked the idea but since Kubernetes is a big beast, that translates to added complexity and steeper learning curve.
Picking up gauntlets is the part of my mission and without realising it, I found myself skimming through Kubernetes GitHub repository and contribution guide.
It would be injustice if I started contributing to Kubernetes before having rudimentary idea about what it does and how does it do that. While I by no means admire official Kubernetes Tutorials but they do a good job of navigating you through basics and even giving a trivial hands on experience for deployment, setting up a pod, creating a cluster and auto-scaling.
Finishing Go on the first day and Kubernetes on second day does sound like utterly inspiring and magical. Btw did I tell you that I have signed up license for contributing to Kubernetes, Yes that’s the first step before submitting a single Merge Request. ‘When you want to achieve something, the whole world conspires again you to help you achieve that’; I tried sleeping at 12 yesterday and after grueling 2 hours of unsuccessful attempt, I gave up, pulled out my Linux machine and started exploring open issues on Kubernetes which were marked as 'Good first issue' aka good for someone who wants to submit his first merge request.
Contributing first few lines of code seems more difficult which I underestimated in the beginning and it seems I need to spend some more time understanding the code.
Once it dawned upon me I went to sleep 😛
Read the next post. Read the previous post.
This post is part of accelerated learning project, Outpacing the fast-paced world.
If you want to follow along with my daily posts, make sure to follow this Medium account.
