|
Question: How does Kubernetes handle networking between Pods?
|
Answer: Kubernetes assigns each Pod a unique IP address within the cluster and manages networking through a
Container Network Interface (CNI) plugin. Every pod gets its own IP address.
Containers within a pod share the pod IP address and can communicate freely with each other.
Pods can communicate with each other directly via these IP addresses,
regardless of the node they are running on.
|
|
Question: What is a Kubernetes Operator?
|
Answer: A Kubernetes Operator is a method of packaging, deploying, and managing a Kubernetes application.
It uses custom resources to extend Kubernetes functionality and automate the management of complex stateful applications,
such as databases, by encoding domain-specific knowledge into software.
|
|
Question: Can you explain Kubernetes Persistent Volumes (PVs) and Persistent Volume Claims (PVCs)?
|
Answer: The Persistent Volumes (PVs) are storage resources in Kubernetes that exist independently of any Pod and can be
dynamically provisioned or statically configured.
Persistent Volume Claims (PVCs) are requests made by Pods for specific storage resources, allowing them to consume PVs
and abstracting away the underlying storage implementation.
|
|
|
|
|
|
Question: What is Horizontal Pod Autoscaling in Kubernetes?
|
Answer: The Horizontal Pod Autoscaling (HPA) is a Kubernetes feature that automatically scales the number of
Pod replicas in a Deployment, ReplicaSet, or StatefulSet based on observed CPU utilization or custom metrics.
It helps maintain optimal resource utilization and application performance under varying workloads.
It changes the workload by automatically increasing or decreasing number of Pods in response to the CPU or memory consumption,
or in response to custom metrics reported from within Kubernetes or any external metrics as available from an outside source.
|
|
Question: Can you describe the concept of Kubernetes Ingress?
|
Answer: The Kubernetes Ingress is an API object used to manage external access to services running in a
Kubernetes cluster. It acts as a traffic router, allowing external traffic to reach services based on rules defined
by the user, such as hostnames, paths, or TLS termination.
|
|
Question: What is a Helm chart in Kubernetes?
|
Answer: The Helm is a package manager for Kubernetes that simplifies the deployment and management of applications.
It automates the creation, packaging, configuration, and deployment of Kubernetes applications by combining your configuration files
into a single reusable package.
A Helm chart is a collection of pre-configured Kubernetes resources packaged together, allowing for easy installation,
upgrades, and management of complex applications.
|
|
|
|
|
|
Question: Can you explain the difference between a DaemonSet and a Deployment in Kubernetes?
|
Answer: A DaemonSet ensures that a specific Pod runs on each node in the cluster, typically used for system-level daemons
or logging agents that need to run on every node. A Deployment manages a set of identical Pods and enables rolling updates
and rollbacks, what typically is used for stateless applications.
|