This is a case study in why there's the word "dev" in devops. While Kubernetes gets really far towards giving you all the dials you need, at the end of the day those dials are the result of low-level code, and of people who made specific (and often well-documented) assumptions in tooling repository pull requests and RFC processes. Just like an application developer might debug or work around an issue with a library dependency by looking at its source code and understanding the nuance of the extension points that exist, and contribute documentation updates or new extension points upstream, a devops team should be empowered to do the same.<p>And from my experience devops is a really welcoming community - people take great pride in making sure their infrastructure tooling covers unorthodox use cases, and meeting them as a collaborator (not just an end user) can be incredibly fulfilling for all involved.<p>(That said, yak shaving is definitely a risk, especially since testing can be complicated with these systems when making low-level tweaks. But it's still often useful to roll up one's sleeves and read Go code rather than just restricting oneself to coloring within the existing configurability lines.)