codingstuff.io
ExploreTutorialsProblemsCS Subjects
Get Started
ExploreTutorialsProblemsCS Subjects
Get Started
codingstuff.io

Master the art of building software through interactive tutorials, real-world problems, and guided projects.

Pune, Maharashtra, India

codingstuffmail@gmail.com

Product

  • Explore
  • Tutorials
  • Problems
  • CS Subjects

Company

  • About
  • Contact
  • Privacy Policy
  • Terms & Conditions
  • Sitemap

© 2026 codingstuff.io. All rights reserved.

Built with ❤️ for developers everywhere

/
/
All Tutorials
☸️

Kubernetes

47 / 82 topics
46Kubernetes Frequently Asked Questions (FAQ)47Kubernetes Glossary48Kubernetes API Reference49Kubernetes Version Compatibility50Kubernetes Roadmap
Tutorials/Kubernetes/Kubernetes Glossary
☸️Kubernetes

Kubernetes Glossary

Updated 2026-05-15
10 min read

Kubernetes Glossary

Introduction

Welcome to the Kubernetes Glossary! Kubernetes is a powerful platform for automating deployment, scaling, and management of containerized applications. Understanding its terminology is crucial for effectively using Kubernetes. This section will provide you with a comprehensive list of key terms and concepts used in Kubernetes.

Concepts

Pod

A Pod is the smallest deployable unit in Kubernetes. A Pod encapsulates one or more containers that share storage, network, and IPC (Inter-Process Communication) resources. Pods are designed to run closely together and share dependencies.

Example:

apiVersion: v1
kind: Pod
metadata:
  name: example-pod
spec:
  containers:
  - name: nginx
    image: nginx:latest

Deployment

A Deployment is a higher-level abstraction that manages the lifecycle of Pods. It ensures that a specified number of identical Pods are running at any given time.

Example:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: example-deployment
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:latest

Service

A Service is an abstraction that defines a logical set of Pods and a policy by which to access them. Services enable communication between different components within the cluster.

Example:

apiVersion: v1
kind: Service
metadata:
  name: example-service
spec:
  selector:
    app: nginx
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80

Namespace

A Namespace is a virtual cluster that provides a way to divide cluster resources between multiple users or teams. Each Namespace operates independently of others.

Example:

apiVersion: v1
kind: Namespace
metadata:
  name: development

ConfigMap

A ConfigMap is an API object used to store non-confidential data in key-value pairs. Pods can consume ConfigMaps as environment variables, command-line arguments, or configuration files.

Example:

apiVersion: v1
kind: ConfigMap
metadata:
  name: example-config
data:
  database_url: "http://database.example.com"

Secret

A Secret is an API object that stores sensitive information such as passwords, OAuth tokens, and SSH keys. Secrets are designed to be more secure than ConfigMaps.

Example:

apiVersion: v1
kind: Secret
metadata:
  name: example-secret
type: Opaque
data:
  password: cGFzc3dvcmQ=

Ingress

An Ingress is an API object that manages external access to the services in a cluster, typically HTTP and HTTPS. It provides load balancing, SSL termination, and name-based virtual hosting.

Example:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
spec:
  rules:
  - host: www.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: example-service
            port:
              number: 80

Horizontal Pod Autoscaler (HPA)

An HPA automatically adjusts the number of Pods in a Deployment, ReplicaSet, or Replication Controller based on observed CPU utilization or other select metrics.

Example:

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: example-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: example-deployment
  minReplicas: 1
  maxReplicas: 10
  metrics:
  - type: Resource
    resource:
      name: cpu
      target:
        type: Utilization
        averageUtilization: 50

What's Next?

For a deeper understanding of Kubernetes API Reference, you can explore the official Kubernetes API documentation. This resource provides detailed information about all the available resources and their APIs.

By mastering these terms and concepts, you'll be well-equipped to navigate and utilize Kubernetes effectively for your containerized applications.


PreviousKubernetes Frequently Asked Questions (FAQ)Next Kubernetes API Reference

Recommended Gear

Kubernetes Frequently Asked Questions (FAQ)Kubernetes API Reference