How can I make our Kubernetes stack easier for app developers to use?

November 16, 2026 4 answers
Asked by Kavren+8j

I'm the default owner of an on-premises Kubernetes stack, and another team's developers will be using it for highly available containerized services. They have bought into using Kubernetes, but other system administrators have little interest in learning it, and the developers may not want to become kubectl experts.

I'm looking at replicas, scheduling and automated patching, plus Tanzu Mission Control. CI/CD hasn't been approved. What would help make the platform usable and supportable?

Answers

9h~claspwrench_417

Start with the developers' actual deployment and support needs, rather than a list of Kubernetes features to teach. What do they need to deploy, check when something fails, and change without waiting for the platform owner?

The stack is already there, but that doesn't mean every team needs to become a Kubernetes specialist. Agree on what the platform team owns and what the application team owns, then use those boundaries to decide what tooling and documentation would help.

Reply to this answer
_b29~circuitmuffin.4

Replicas are a useful starting point for availability, but having multiple pods alone doesn't guarantee a service stays available during maintenance. Test how workloads behave when nodes are patched and whether replicas are placed so one node going down doesn't take them all with it.

Taints and tolerations control which pods can be scheduled on certain nodes. They aren't a patching strategy by themselves. Give developers a simple example workload with the replica and scheduling settings you've tested, and explain which parts they need to choose for their application.

Reply to this answer
Rilvek-2m

Consider GitOps for managing deployments. Flux is one option to evaluate, rather than assuming a traditional CI/CD pipeline is the only route. Since CI/CD hasn't been approved, check what approval a GitOps workflow would need before building around it.

Reply to this answer
6p!corkratchet_508

A management interface could lower the barrier for people who don't want to use kubectl for every task. Compare Tanzu Mission Control with other interfaces against the things developers and administrators actually need to see and do. Radar is another option to look at.

Access still needs thought. Decide who can view workloads and who can make changes instead of treating the interface as a substitute for permissions or operational knowledge.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions