First time, I joined the the kubernetes community slack, sometime in the middle of june, 2020.
I started there by getting involved with the (then) newly formed, node-reviewers-group. This was kind of a mentorship program where a group of people would work together on reviewing/triaging sig-node
PR(s) & issue(s).
I spent couple of months in the group, trying to understand all what was being taught (or discussed) in there. I soon realised I was not able to understand much of the stuff at the time. I was too overwhelmed by the concepts being discussed there, that I felt absolutely alien-ish in that space. So, in the end, I just gave up & left.
Which was not good, I should have tried more. But anyway, I’m back on the track after 6 months now!
I’ve started my journey again. And this time, I’m very actively getting involved into various parts of the Kubernetes organisation.
This document will be a running logging document for all my upstream Kubernetes project contributions.
So, Let’s start then…
(For someone who want to read from the beginning, start here.)
PR(s)
PR(s)
PR(s)
PR(s)
vmware-tanzu/community-edition
PR(s)
vmware-tanzu/cluster-api-provider-bringyourownhost
PR(s) merged
Issues resolved
Issues (WIP)
Issues reviewed/triaged
kubernetes organisation membership request
🎊
PR(s) merged
PR(s) merged
PR(s) merged
PR(s) merged
PR(s) merged
Issues resolved
Issues assigned
PRs raised
Issues resolved
Issues created & resolved
Issues/PRs responded to
I first started writing kubernetes flavor of go code while working on the integreatly-operator project. This is an Openshift Operator based on the Operator SDK for installing and reconciling Integreatly services.
PR(s) merged
This was my very first time contributing on the upstream kubernetes project.
PR(s) merged