Loft Labs Integrates Argo CD with Kubernetes Virtual Clusters


During the KubeCon + CloudNativeCon North America conference, Loft Labs announced that it has integrated the virtual instances of the Kubernetes clusters it enables with the open source Argo continuous delivery (CD) platform.

The goal is to make it easier for DevOps teams to create a virtual cluster that can be turned on and off by creating lightweight Kubernetes clusters that run in the namespaces of a larger physical Kubernetes cluster.

Loft Labs CEO Lukas Gentele said more than 20 million virtual clusters have been created in the past 12 months using the open-source vcluster software the company created when IT teams discovered that Not all Kubernetes use cases require a dedicated cluster. Instead, IT teams set up a handful of physical clusters that can be easily partitioned using vcluster, he says.

One of the primary use cases for vcluster edition supported by Loft Labs is to create self-service development environments where developers can build, test, and debug cloud-native software using of an ephemeral DevOps environment. In addition to Argo support, Loft Labs previously added integrations with open-source Terraform infrastructure-as-a-code (IaC) software as well as GitHub’s DevOps tools.

These integrations make it easier for organizations to adopt GitOps best practices that revolve around CD platforms running on Kubernetes clusters. That’s because Argo, for example, can now be deployed with just one click, Gentele notes. This is critical as organizations seek to balance the need to centrally manage DevOps environments running on Kubernetes clusters with the desire for autonomy for development teams to extend toolchains as they see fit. seems for a given individual project, he adds. In fact, the only reason many development teams choose to manage their own Kubernetes clusters is to preserve their own autonomy, usually at the expense of being able to spend more time writing the actual application code.

It is unclear how many virtual Kubernetes clusters appear in pre-production environments versus applications running after deployment. Obviously, many of the benefits of virtualization can be applied to Kubernetes clusters in the same way virtual machines are used to increase server utilization rates. Virtual clusters, in fact, offer the added benefit of allowing IT teams to significantly reduce the potential for Kubernetes proliferation, as it is now possible to create clusters with a multi-tenant environment. Most organizations are also more sensitive to these Kubernetes costs during the economic downturn. Rationalizing existing Kubernetes clusters represents an opportunity for IT teams to reduce the total cost of IT in a way that simultaneously improves overall productivity.

One way or another, DevOps teams are tasked with improving the overall experience of app developers. Abstraction layers, such as a vcluster, will inevitably play a critical role in enabling organizations to achieve this goal at a time when many developers still do not want to manage IT operations themselves.


Comments are closed.