|
Question: What are Kubernetes Custom Resource Definitions (CRDs), and how are they used?
|
Answer: Kubernetes Custom Resource Definitions (CRDs) enable users to define custom types of resources beyond
the built-in Kubernetes objects. CRDs allow for the extension of the Kubernetes API with domain-specific resources, enabling
the creation of custom controllers and operators to manage these resources.
|
|
Question: Can you explain the concept of Kubernetes Pod Overhead?
|
Answer: The Kubernetes Pod Overhead refers to additional resource overhead incurred by system daemons and processes
running alongside user containers within a Pod.
This overhead includes resources such as CPU, memory, and filesystem usage, which should be considered when sizing nodes
and setting resource limits.
|
|
Question: What is Kubernetes Pod Preset, and how does it work?
|
Answer: The Kubernetes Pod Preset is a mechanism for predefining and injecting Pod configuration settings,
such as environment variables or volume mounts, into Pods at runtime.
Pod Presets are useful for setting default configurations or sharing common settings across multiple Pods within a namespace.
|
|
|
|
|
|
Question: What is Kubernetes Pod Priority and Preemption?
|
Answer: Kubernetes Pod Priority and Preemption is a feature that allows Pods to be assigned priority levels,
ensuring that higher-priority Pods are scheduled and maintained ahead of lower-priority Pods.
Preemption automatically evicts lower-priority Pods to make room for higher-priority Pods when resources become scarce.
|
|
Question: What are Kubernetes Affinity and Anti-Affinity rules and how are they used?
|
Answer: Kubernetes Affinity and Anti-Affinity rules influence the scheduling of Pods based on node or
Pod labels, ensuring that Pods are scheduled together or apart from certain other Pods or nodes.
Affinity rules specify requirements for co-location, while Anti-Affinity rules specify preferences
or requirements for avoiding co-location.
|
|
Question: Can you explain the difference between Kubernetes Jobs and CronJobs?
|
Answer: The Kubernetes Jobs are used to run one-off or batch tasks to completion, ensuring that a specified
number of Pod instances complete successfully before terminating.
CronJobs, on the other hand, are used to run Jobs on a recurring schedule, similar to the Unix cron utility,
allowing for periodic execution of tasks.
|
|
|
|
|
|
Question: What are Kubernetes Service Types, and how do they differ?
|
Answer: The Kubernetes Service Types define how services are exposed outside the cluster and how they can be accessed
by other services or external clients. The common Service Types include:
ClusterIP: Exposed only within the cluster.
NodePort: Exposed on a static port on each node.
LoadBalancer: Provisioned external load balancer.
ExternalName: Maps services to external DNS names.
|