The widespread use of cloud-native applications, and therefore containers, has resulted in the development of numerous container orchestration tools, among which HashiCorp’s Nomad and Kubernetes stand out.
In recent years, Kubernetes has become the preferred choice for companies looking to run and manage large containerized workloads in an automated way. Kubernetes is an open source solution that was built to address the inherent shortcomings of running containers at scale in areas such as deployments, scaling of workloads, managing the underlying infrastructure, load balancing, and other networking components.
I did an introductory talk for PlatformCON about virtual Kubernetes clusters and the open source tool vcluster. vcluster allows you to create and manage virtual clusters, which are basically a control plane inside of a namespace on a shared host cluster.
We’re proud to announce our new terraform provider for Loft. For customers already managing infrastructure using Terraform, the terraform-provider-loft allows configuring Loft spaces and virtual clusters as terraform resources.
The latest episode of VMWare’s TGIK stream featured a hands-on look at vcluster. You can watch the recording below. If you’re not familiar with vcluster, it improves the Kubernetes multi-tenancy experience by letting users run virtual Kubernetes clusters inside a shared host cluster.
Without automation, launching a new product or improving an existing infrastructure is often an uphill task. Luckily, there are many automation tools available to make your project lifecycle more efficient.
For developers to be efficient, they need a strong setup, good habits, and tools they know and love to use. With all these ingredients, they’ll feel good about their workflow and focus more intensely on the products they’re building, which will help them more swiftly achieve their goals.
Authentication helps control access to cluster resources by first verifying a user’s identity. In Kubernetes, the API server needs to verify the identity of every request it receives.
If you’ve worked with consistently growing development teams, there is a high chance that you have come across the complexities of managing dozens of tools and technologies such as containers, microservices, cloud resources, codebases and much more to reduce the DevOps overhead.
As your organization grows, deploying your software and maintaining all related systems can become more complex. This complexity, along with the desire to own the infrastructure stack without needing workarounds for off-the-shelf tools, drives many teams to implement an internal developer platform (IDP).
Are you planning to deploy a database in the Kubernetes cluster? If so, then you’ve come to the right place. Kubernetes is a container orchestration tool that uses many controllers to run applications as containers (Pods).
Earlier this year, at my company, we hit a wall while developing a web application for a client. We had very limited finances and needed someone to support the DevOps side of things.
Self-hosting is, by no stretch of the imagination, a new concept. For many years, engineers and IT admins have been looking into how they can self-host their tools.
The way we do business has drastically changed over the past few decades as more industries go digital. More fault-tolerant and highly scalable systems, quicker responses to defects, and frequent upgrades call for accelerated delivery and increased productivity from our development teams.
Regardless of the infrastructure you are running, it is always important to keep an eye on your costs. There have been enough horror stories of cloud billing getting out of control that teams should have some measures in place to keep an eye on the usage of these resources to avoid surprises.
Kubernetes is a powerful tool with a lot of functionality, but sometimes you might need to extend that functionality to suit your use case better. This is where Custom Resource Definitions (CRDs) come in.
Kubernetes is the third most loved platform by developers, according to the Stack Overflow 2020 Developer Survey, but it’s still quite complex to use. That complexity can impede workflow.
With Kubernetes becoming the gold standard for advanced container orchestration, it’s also become necessary to use extensions that work alongside Kubernetes to provide security and modularity.
Recently, you might have heard about “internal Kubernetes platforms” from many different sources: KubeCon talks, blog articles, or just colleagues and friends. Even if such platforms are not always called internal Kubernetes platforms, solutions that allow engineers to get a standardized and easy Kubernetes access in a cloud environment seem to become more common now.
The container orchestration technology Kubernetes has become the dominant solution for cloud infrastructure and as such it is maturing at an unrivaled pace. Many companies have already adopted Kubernetes or are in the process of it.
Kubernetes is everywhere. You can easily get this feeling if you hear about one of its many impressive adoption figures. Does that mean that Kubernetes has reached its “final stage” and already brings all its benefits to the companies using it?
Kubernetes has matured so much recently that it even expanded beyond its original space as operations technology. So, also at least 1.7 million developers are already using Kubernetes as “The State of Cloud Native Development” by the CNCF stated for Q2 2019.
Adopting Kubernetes is a process that many companies are currently going through. The introduction of Kubernetes as infrastructure technology can take some time. (It took almost 2 years for Tinder to complete its migration to Kubernetes.