Re:The Guide to Kubernetes Labels
by GauntletWizard on Wednesday September 01, 2021 @03:49PM
(#28384759)
I wouldn't use it on a pod directly, but I recommend that annotations on deployments include the oncall rotation that is responsible for them - And there's no real reason not to cascade that down onto pods as well.
[ Parent
| on HN ]
Interesting, do you have an example how this would look like?
Re:The Guide to Kubernetes Labels
by GauntletWizard on Wednesday September 01, 2021 @05:00PM
(#28385460)
Just "company.com/pagerduty-service" as a "required" annotation (i.e. if you forget your namespace's team gets a reminder at their E-mail, which is another required annotation)
Namespace onboarding is self-service by pull request: a template namespace is in the readme, and contains a number of standard annotations like ldap group and etc. The kubernetes admin team accepts and merges those requests and the bot deploys the namespace folder to the clusters.
This is basically zero overhead at small groups and scales well to giant companies, you just add annotations and sometimes labels as business requirements and structure dictate.