YAKDT: Yet Another Kubernetes Development Toolkit

Madokai
Geek Culture
Published in
10 min readDec 8, 2021

--

This article is in line with our latest article «YAKD: Yet Another Kubernetes Dashboard» in which we listed several dashboard projects dedicated to managing Kubernetes clusters. In this article, we focused on development tools and we tried to highlight considerations that everyone should have in mind to correctly identify which tool is the best in which context.

Every SRE, DevOps engineer, developer and Kubernetes operator had to answer this question at least once in their life: what tool would be the best to manage my Kubernetes resources?

There is obviously not a single answer to this question because it depends on multiple factors as developers and operators have a different way of consuming Kubernetes resources. One wants to focus on speed, while the other potentially focuses on security and automation aspects.

Important Considerations

Several considerations should be taken into account when choosing the tools used to operate and consume Kubernetes resources. Operators and developers have, by their trade, a different use of this platform and therefore, potentially require a different client to handle their resources.

Unlike developers, operators have constraints to respect or impose to ensure the sustainability of the cluster and compliance with mandatory security policies while allowing easy access to resource management.

On the development side, the constraints are higher. The aim is to minimize infrastructure constraints and friction so that it accelerates the development of new features.

Identifying and understanding each person’s needs is necessary in order to work harmoniously as a team.

Several considerations must therefore be taken into account when choosing such tools:

  • The level of maturity of the teams is obviously an important factor in the choice of the tool. Ease of access to Kubernetes management is paramount to ensure the adoption and proper use of resources.
  • User Interface (UI) versus Command Line (CLI), this aspect is generally unique to each one but can be an important factor stemming from the maturity of the teams regarding the management of Kubernetes.

--

--

Madokai
Geek Culture

DevOps, Observability, Cloud Computing and Automation!