Explanation:
What is etcd? etcd is a strongly consistent, distributed key-value store that provides a reliable way
to store data that needs to be accessed by a distributed system or cluster of machines. It gracefully
handles leader elections during network partitions and can tolerate machine failure, even in the leader node.
Explanation:
Kube-scheduler is the default scheduler for Kubernetes and runs as part of the control plane. kube-
scheduler is designed so that, if you want and need to, you can write your own scheduling component
and use that instead. For every newly created pod or other unscheduled pods, kube—scheduler selects
an optimal node forthem to run on.
Explanation:
Master components provide the cluster’s control plane. Master components make global decisions
about the cluster (for example, scheduling), and detecting and responding to cluster events (starting
up a new pod when a replication controller’s ‘replicas’ field is unsatisfied).
Explanation:
Running: Pod has been bound to a node, and all of the containers have been created.
Explanation:
Kubernetes comes with a set of built-in controllers that run insidethe kube-controller-manager. Thesebuilt-in
controllers provide important core behaviors. The Deployment controller and Job controller are examples of
controllers thatcome as part of Kubernetes itself ("built-in" controllers).
Explanation:
Correct Answer None of the above
The kubelet component is an agent that runs on every worker node of the cluster. It is responsible for
managing all containers running in every pod in the cluster. it does this by ensuring that the current state
of containers in a pod matches the spec for that pod stored in etcd.
Explanation:
Labels in Kubernetes are intended to be used to specify identifying attributes of objects that are
meaningful and relevant to users but are not used by the Kubernetes itself. Labels are fundamental
qualities of the object that will be used for grouping, viewing, and operating. Each object can have
a set of key/value labels defined.
Explanation:
The kubelet uses readiness probes to know when a container is ready to start accepting traffic. A Pod is considered
ready when all of its containers are ready. One use of this signal is to control which Pods are used as backends for
Services. When a Pod is not ready, it is removed from Service load balancers.
Explanation:
Each node has at least one Kubelet, an agent that ensures the described containers are running in the pod on
a cluster. Control plane: The orchestration layer that exposes the API you use to manage your containers,
pods, and nodes.
Explanation:
The API server is a component of the Kubernetes control plane that exposes the Kubernetes
API. The API server is the front end for the Kubernetes control plane.
Explanation:
Limits and requests for CPU resources are measured in cpu units. One cpu, in Kubernetes, is equivalent to
1 vCPU/Core for cloud providers and 1 hyperthread on bare-metal Intel processors. Fractional requests are
ALLOWED. A Container with spec.containers [].resources.requests.cpu of 0.5 is guaranteed half as much CPU
as one that asks for 1 CPU.
Explanation:
You can use kubectl patch to update API objects in place. This command supports JSON patch, JSON merge patch,
and strategic merge patch. See Update API Objects in Place Using kubectl patch and kubectl patch.
Explanation:
Limits and requests for memory are measured in bytes. You can express memory as a plain
integer or as a fixed—point number using one of these suffixes: E, P, T, G, M, k. You can
also use the power-of—two equivalents:
Explanation:
Kubernetes doesn't specify a logging agent, but two optional logging agents are packaged with the Kubernetes release:
Stackdriver Logging for use with Google Cloud Platform, and Elasticsearch. You can find more information and instructions
in the dedicated documents. Both use fluentd with custom configuration as an agent on the node.
Explanation:
Kubelet is an agent or program which runs on each node. This is responsible for all the communications between
the Kubernetes control plane [group of programs which control kubernetes] and the nodes where the actual
workload runs.
Explanation:
Kubectl controls the Kubernetes Cluster. It is one of the key components of Kubernetes which runs on the workstation
on any machine when the setup is done. It has the capability to manage the nodes in the cluster.
Explanation:
Replication Controller is one of the key features of Kubernetes, which is responsible for managing the pod lifecycle.
It is responsible for making sure that the specified number of pod replicas are running at any point of time.
Explanation:
metadata - Data that helps uniquely identify the object, including a name string, UID, and optional namespace spec -
What state you desire for the object The precise format of the object spec is different for every Kubernetes object,
and contains nested fields specific to that object.
Explanation:
Minikube is a tool that makes it easy to run Kubernetes locally. Minikube runs a single-node Kubernetes
cluster inside a VM on your laptop for users looking to try out Kubernetes or develop with it day-to-day.
Explanation:
Kube-proxy is a network proxy that runs on each node in your cluster, implementing part of the Kubernetes Service
concept. kube-proxy maintains network rules on nodes.
Explanation:
The API server is the front end for the Kubernetes control plane. The main implementation of a Kubernetes API server
is kube-apiserver. kube-apiserver is designed to scale horizontally—that is, it scales by deploying more instances.
Explanation:
An object definition in Kubernetes requires an apiVersion field. When Kubernetes has a release that updates what is
available for you to use—changes something in its API—a new apiVersion is created. However, the official Kubernetes
documentation provides little guidance on apiVersion.
Explanation:
The correct answer is shared context
Explanation:
To set environment variables, include the env or envFrom field in the configuration file. In this exercise, you
create a Pod that runs one container. The configuration file for the Pod defines an environment variable with
name DEMO_GREETING and value "Hello from the environment".
Explanation:
Node controller: Responsible for noticing and responding when nodes go down.
