---
# System prepended metadata

title: What You Might Not Know About Kubernetes

---

![](https://i.imgur.com/PruWu0H.jpg)
# What You Might Not Know About Kubernetes
>A quick dive into what might be the things you do not know about Kubernetes

Kubernetes, known as an open source platform which automates Linux container operations, getting rid of its perplexity basically helps one in managing clusters of hosts running containerised applications smoothly and efficiently.

What makes Kubernetes an ideal platform to support native cloud apps requiring rapid scaling is the feasibility to have hosts across public, private or even hybrid clouds.

Google has been one of the early contributors to Linux container technology and the genesis to Kubernetes. Pretty good for us how Google has been quite open about everything in containers, technology behind Google's cloud services.

Now, let's spill the beans and talk about 5 things that you might not know about Kubernetes.

## The K8S Story

Kubernetes is also abbreviated as k8s. This is based on the numeronym system of naming that began in the early 80s. 
It's based on a straightforward method, as you would've guessed by now. You keep the first and last alphabet of the word and put a number in place of rest of the letters.
Hence, Kubernetes becomes "k" + 8 + "s" and _voila_! k8s. 

![](https://i.imgur.com/s8GoWKr.jpg)
>Kubernetes talk at Google Cloud Summit | Source: Raysonho via Wikimedia Commons

## State: less or full?

Kubernetes, created originally for stateless applications also supports the concept of persistent volume, its claims and a bunch of other types of volumes as well.

## Hybrid cloud deployment

Initially, k8s only supported deployment in one datacenter. However, later, development of the kubernetes foundation allowed a hybrid scenario where several k8s clusters can be controlled right from a single control panel.

_Pretty cool, right?_ 

![](https://i.imgur.com/9NADJI8.jpg)

## The pod and container difference

Individuals coming from docker to k8s might only be well versed with containers. However, in Kubernetes, the control unit is a pod, which can be termed as a group of containers deployed together on the same host.

A pod's contents always exist in a shared content and are co-located as well as co-scheduled. 

![](https://i.imgur.com/abtYVQx.jpg)

## Simplification of containerised development

Kubernetes does this by offering built-in service discovery, using a rolling update strategy for rolling out pod version updates and offering flexible manifests for the deployment of applications supporting different deployment strategies of container applications. 

This is followed by canary deployment support for A/B tests, built-in health checks and prometheus-based monitoring. 

_That's pretty neat!_

