5 Key Elements for a Great Developer Experience with Kubernetes

Two women looking at a white board

Use Tools for Local Development

  • Skaffold, developed by a team at Google, offers a local continuous integration/continuous delivery (CI/CD) experience for Kubernetes. Skaffold can get your team started in one command line if they have an existing Dockerfile or Kubernetes manifest. Then they can build, test, and deploy their application to their local Kubernetes. This makes the testing process much faster and more reproducible since they are already testing the code running inside a Kubernetes cluster. Skaffold offers an interesting option for those who want to move from a Docker and Docker Compose local setup to a Kubernetes one.
  • DevSpace is very similar to Skaffold in terms of features, with the added benefits of a dedicated UI and a two-way file sync. The UI gives your team an overview of the stack and easy access to logs. At the same time, the file synchronization feature makes their development process faster by letting them directly change code from a running container.
  • Tilt also lets your team build, test, and deploy microservices to their local Kubernetes. It facilitates developer onboarding with Kubernetes with a highly customizable UI. They can have extra buttons to run tasks and streamline QA testing and automate repeating tasks (such as clearing the database or loading a data set).

Enable Self-Service for Everything

Set Soft Limits and Hard Limits

Maintain a Product Mindset

  • Make data-driven decisions: instrument your platform, collect metrics, survey the developer on what can be improved. For instance, you could implement DORA metrics and regularly check whether the platform is getting you closer to the top performer on the market.
  • Prioritize continuous evolution: capture and analyze new trends or products. Then curate the most promising options, add them to your self-service, and empower teams to use the latest technologies.
  • Ensure customer delight: treat the internal platform with the same level of attention that you would provide to your end user. Test your changes, minimize operational impact, and try to reduce the number of interventions from the Kubernetes operations teams.

Account for Different Experience Levels

Conclusion

--

--

--

>> www.loft.sh << Build Your Internal Kubernetes Platform With Virtual Clusters, Namespace Self-Service & Secure Multi-Tenancy

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Modular Architecture with MVVM-C + SPM + SwiftUI in iOS

TensorFlow Object Detection Faster CS:GO Aim Bot

Anatomy of a Supreme Bot (Part 2)

Get all GitHub Repos with PowerShell

No, the problem isn’t “bad coders”

Android Oreo: all you need to know

Two Weeks In

Delayed messages with RabbitMQ in Node

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Loft Labs

Loft Labs

>> www.loft.sh << Build Your Internal Kubernetes Platform With Virtual Clusters, Namespace Self-Service & Secure Multi-Tenancy

More from Medium

5 Ways to Access Kubernetes Clusters

Overhead photo of a multi-lane freeway

My top 8 commands and tools for debugging applications running on Kubernetes

Kubernetes: open source production-grade container orchestration management

Falco: A Security Camera For Kubernetes Applications

DevOps / SRE — Top Links Last Week