Maintaining standards

Open standards can make or break a Kubernetes implementation

Adopting open standards for Kubernetes is relatively easy to do. Maintaining these standards, however, requires your team to be active and vigilant. To implement open standards correctly, DevOps teams need to appraise the existing standards, understand how they can lapse within an organisation, and appreciate the importance of working with the open source community to create and maintain the standards.

The next step forward

How developers can go Kubernetes-native

Kubernetes orchestrates the relationships between all of the containers in a system, such as communication and resource allocation. This article by Markus Eisele examines how to become Kubernetes-native and much more flexible.

Kubernetes Probes

Kubernetes: How to use readiness, liveness, and startup probes

A pod is the smallest unit in Kubernetes. It is a container for containers that are running in a shared context like the same host, same IP etc. The status of the containers can be checked by so called probes. The respective results are then aggregated to the status of a pod by Kubernetes. A probe is a diagnosis that is made regularly by the Kubelet on a running container. To perform this diagnosis, the Kubelet calls an endpoint implemented by the container process or executes a binary in a container. The Kubelet can perform and react to three types of probes: Readiness, Liveness and Startup.

Set sail for 1.18

Kubernetes 1.18 includes 38 enhancements under the hood

There’s no denying the vast popularity of Kubernetes. The newest version is here with the release of Kubernetes 1.18. In total, it includes 38 enhancements, many of which have graduated to GA. Let’s take a look at what this powerhouse brings to the table with version 1.18.