CLI – Command Line Interface. Screen where you enter code to launch and make changes to your Kubernetes cluster.

DevOps. An emerging practice affecting IT operations people that typically work in application delivery. Emphasis on automation, coding infrastructure and cloud tooling.

K8s. Shortened term for Kubernetes. Much more efficient to type in Slack chats than all 10 characters.

Load Balancer. Networking solution that makes sure that incoming traffic is evenly distributed among replica containers and nodes.

Node. Kubernetes interpretation of a virtual machine (VM) or a physical machine. Each node can host multiple pods, which in turn can run multiple containers.

Operator. Extension (like a tool) for enhancing Kubernetes capability or functionality e.g. Prometheus, Jaeger. They rely on custom resources not within the Kubernetes codebase.

Pod. Smallest unit within Kubernetes. Instance that hosts several containers within it.

Secret. Storage for sensitive information such as passwords, OAuth tokens and SSH keys.

Self Healing. State where an application component detects that is it not function to spec. It then begins a process of repairing itself or mitigating risk from defects.

Shift Left. Refers to a strategy of making developers responsible – or at least aware of – everything that comes after their work. That means testing, deployment, security etc.

Sidecar. Container that supports the other containers within the pod. Examples include service meshes like Istio and LinkerdD, as well as Jaeger for tracing.

Site Reliability Engineering. Google concept of proactive IT operations vs. reactive approach of old-school sysadmins. Automate rather than manually do. Prevent rather than fix.

SLO. Abbreviation for Service Level Objective. It’s a numerical performance target for metrics like uptime. Most often used in Site Reliability Engineering. More info via Google