by Daniel Thiry

The idea of virtual Kubernetes clusters (vClusters) is to spin up a fully-functional cluster within another Kubernetes cluster to provide an efficient abstraction and direct Kubernetes access on top of a shared underlying cluster.

I have already described the benefits and use cases use of such virtual clusters for development, and specifically for cloud-native development, CI/CD, and ML/AI experimentation. However, since vClusters are similarly flexible as regular Kubernetes clusters and namespaces, they can also be used in many situations apart from development.

In this article, I want to describe some of these production use cases that I…


by Daniel Thiry

Virtual Kubernetes Clusters (vClusters) have the potential to bring Kubernetes adoption to the next level. They are running in a physical Kubernetes cluster and can be used in the same way as normal clusters, but still are just a virtual construct. (Learn more about how virtual Clusters work here). Similar to Virtual Machines that revolutionized the use of physical servers, virtual Kubernetes clusters have some benefits compared to physical clusters, which make them particularly useful for some scenarios.

In this article, I will describe the benefits of virtual Kubernetes clusters and provide some use cases in which…


by Rich Burroughs

Hi, I’m Rich Burroughs, and I’ve just joined Loft Labs as a Senior Developer Advocate. I’m very excited to be here, and I’d like to share a bit about why I joined the team.

Multitenancy in Kubernetes is a nightmare. Everyone knows it. Namespaces are great but they don’t provide the isolation that a lot of teams need. A developer who has access to a namespace can’t manage things like CRDs, which live outside the namespace, or see cluster-wide resources.

What this leads to is one of two results, which are both pretty painful. Either you use…


by Daniel Thiry

Many companies have adopted Kubernetes recently. However, most of them still do not realize its full potential because the actual Kubernetes usage in these organizations is very limited. Since Kubernetes has evolved dramatically, it is now not only a technology for operations anymore but also non-ops engineers can work with it. For this, Kubernetes adoption should not end here, it rather just starts.

So, it now often makes sense to also include engineers in the Kubernetes adoption process and, as the latest Stack Overflow Developer Developer Survey shows, engineers appreciate it as they both want to work…


by Daniel Thiry

Kubernetes has left the state when it was mostly an ops technology behind and now is also very relevant for many developers. As I wrote in my blog post about the Kubernetes workflow, the first step for every developer who starts to directly work with Kubernetes is to set up/get access to a Kubernetes development environment.

A Kubernetes work environment is not only the first step but also a basic requirement to be able to work with Kubernetes at all. Still, access to such an environment is often a problem: A VMware study even found out that…


by Levent Ogut

Kubernetes has been disruptive due to the scalability, velocity, portability, and observability it adds to cloud deployments. While it brings a whole ecosystem of great features and options and eases complex deployment, it also has its own challenges. One of the great features Kubernetes has brought us is that of high availability. There are many high availability options in Kubernetes; in this article, we will discuss high availability options used for the application/microservice itself.

Pods — the smallest deployable units in Kubernetes — are scheduled once the declarative configuration is applied. Kube-scheduler is responsible for the calculation…


by Levent Ogut

Kubernetes brought an excellent deployment platform to work on. Even monolithic applications can be run in a container. For some of these monolithic applications and for some microservices, a slow start is a problem. Even if we configure readiness and liveness probes using initialDelaySeconds, this is not an ideal way to do this. For this specific problem, startup probes are developed.

Probes

Probes are executed by kubelet to determine pods’ health.

All three types of probes have common settings to configure.

  • initialDelaySeconds: How many seconds to wait after the container has started (default: 0)
  • periodSeconds: Wait time between…


by Levent Ogut

Kubernetes has disrupted traditional deployment methods and has become very popular. Although it is a great platform to deploy to, it brings complexity and challenges as well. Kubernetes manages nodes and workloads seamlessly, and one of the great features of this containerized deployment platform is that of self-healing. For self-healing on the container level, we need health checks called probes in Kubernetes unless we depend on exit codes.

Liveness probes check if the pod is healthy, and if the pod is deemed unhealthy, it will trigger a restart; this action is different than the action of Readiness…


by Levent Ogut

Kubernetes is a great platform to deploy our microservices and applications to. One of the excellent features is that pods are restarted or removed from a service when they don’t work correctly. Kubernetes needs our help to understand if a pod is working or not. This is configured via Container Probes.

Any application can be in an unhealthy state due to bugs, missing dependencies on external resources, and so on. To make sure our traffic flows correctly, we need to make sure probes are configured.

Probes are kubelet’s answer to the health checks, there are three handlers:


by Volodymyr Grin

Kubernetes multi-tenancy provides a number of business and technical advantages over single-tenant clusters. However, multi-tenancy also brings several challenges and pain points with it, one of which is handling Kubernetes custom resource definitions (CRDs).

In this post, I will explain some of the biggest headaches typically experienced when dealing with CRDs in a multi-tenant Kubernetes environment as well as ways to minimize these issues.

CRDs & Kubernetes Multi-Tenancy

Let us first go over some key ideas behind custom resource definitions (CRDs), multi-tenant Kubernetes clusters, and how CRDs are handled in a multi-tenant architecture.

What are CRDs?

A custom resource is one way to extend…

Loft

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

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