Notes: sig-auth issues & KEP review, structured-logging workgroup, kubernetes org membership (🎊) #10
May 13, 2021
Quick notes from today:
sig-auth issues & KEP review
- To get better understanding of the work going on in around various kubernetes sig groups, I’m focusing now on reviewing PR/issues & the KEP(s) (Kubernetes Enhancement Proposals).
- My first point of start is
sig-auth. Although, today I went through mix set of PRs & KEPs - I (kind of) reviewed the following PRs from the kubernetes/kubernetes repo, which are labelled as
sig-auth. Well, “kind of” because this is my first time reviewing k8s project PRs, rather than directly putting comments in the PRs, I collected my review notes & doubts in this google doc here. - I (kind of) reviewed the following KEPs from the kubernetes/enhancements repo:
- It was really really really (I can’t emphasize enough) useful exercise. With this much review, I learnt a heck lot about the process followed by different sig(s) while reviewing their PR(s), what things to consider, what questions to ask, what sections to look at or verify & heck lot more. I’ll keep writing more about them, as I start practising them slowly in action!
- Some useful links:
- SIG Node Triage Process
- Where to check the status of the jobs/tests that I ran on my PRs
- Kubernetes: Prow commands help
- How to check what are the kinds/subcommands/value-types available for a prow/bot command
- For ex: in the above ^ case it is checking what are the different kinds of the bot command
/priority
- For ex: in the above ^ case it is checking what are the different kinds of the bot command
- Guide to what all are the labels available & where & when do they get applied
- And lastly again, the elaborated review notes are in this document.
- My first point of start is
structured-logging workgroup
- I attended the first meeting for the
structured-loggingworkgroup. This is definitely something that I’m going to work on very soon (or right away). This is a new working group being created, focusing on:- defining standard structure for Kubernetes log messages,
- add methods to
klogto enforce this structure, - add ability to configure Kubernetes components to produce logs in JSON format
- and finally, initiate migration of kubernetes component logs to structured logging
- Action item (by myself) from today’s meeting for is:
- Thoroughly read through the Structured Logging KEP.
- Slowly slowly go through these PRs for kubelet migration to structured logging
Updates on previous PRs
- PR: update deployment_crud.py to include a restart_deployment method for typed client #1452 is finally merged. It was on hold from more than a week long time just because of the failing (pycodestyle script) job. Everything in the job run logs is green now.
- And this one from yesterday, bump containerd version to v1.5.0 (#606) is also merged now.
kubernetes org membership
- And finally, last & the most wonderful thing for today (I literally danced for an hour, I mean literally)
- Finally, I created the issue for the kubernetes organisation access (and ofcourse, some wonderful folks have sponsered me for my membership 👼)
- So, yes it is on the way but it will happen for sure (hoping before the next post itself 😄)
That’s all stuff from my day today.
It was a work holiday (ah, although, I had on-call duties but fortunately wasn’t paged at all), & I’m happy I utilised my time well (talking, working, learning, dancing & exercising. 🙂)