0% found this document useful (0 votes)
38 views2 pages

Kubernetes Interview Q &A

kubernetes interview questions and answers

Uploaded by

lonka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
38 views2 pages

Kubernetes Interview Q &A

kubernetes interview questions and answers

Uploaded by

lonka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

Ingress & Egress


Ingress is an incoming traffic to the POD.
Expose HTTP & HTTPS routes from outside the cluster to services within the cluster.
Ingress sends all its traffic to one.
2. Egress : It’s a outgoing traffic from POD
3. Restricting Egress Traffic: It’s a common security requirement and best practice to restrict
outgoing connect from the cluster.
4. Outgoing (NAT) behavior: Network Address translation is a process of mapping IP address in a
packet to different as the packet passes through different device performing. (NAT).
5. Egress gateways: Another approach to Kubernetes egress is route outbound all connections via
one or more gateways. The gateways SNAT (Source Network Address translation) the
connections. So the external services being connected to see the connection coming from the
egress gateways.
6. Kubernetes Deployment YAML: It specifies the configuration for the deployment object.
This is Kubernetes objects that can create and update a set of identical pods. Each pods runs
specific containers. Which are defines in the specific template field of the YAML configuration.
7. A Kubernetes deployment YAML specifies the configuration for a deployment object this is
kubernetes object that can create and update a set of identical pods.
8. Daemon Set: - It deploys a pod on all cluster nodes or A certain subset of NODES.
9. State full Set: - Used for state full application. Similar to a deployment but each pod is unique
and has persistent identifier.
10. Expose router: - It navigate to your router configuration page by typing the routers IP address in
to your web browser. Find a sett9ings tab for your port or port forwarding. Where indicates
input the number of port you want to open. Where indicate the input of the static IP address of
the device you want the port to forward to router.
11. Services in Kubernetes :-
A) Cluster IP : Expose the services on a cluster – internal IP … Makes the services only reachable
with the cluster. This is default service type.
B) Node Port: - Expose the services on each node IP at static port. A cluster IP service to which
node port service will route is automatically created.

12. Load balancer:-Expose the services externally using a cloud providers load balancers. Services
to whi9ch the external load balancers will route are automatically routed.

13. External Name: - Maps the service to the contents of the external name fields by returning a
(C NAME) record with its value.. proxying of any kind is setup.
14. Types of LOADBALANCERS :-
A- Internal Load balancers – It automatically balances load and allocates the pods with
required configuration.
B- External Load balancer: - It directs the traffic from external loads to backend pods.

Polling: - It is a library for computing the status of Kubernetes resources based on polling of resource
state from a cluster. It can keep polling until either some condition is met or until it’s cancelled through
provided context.
Election in Kubernetes: - It begins with creation of a lock object where the leader updates the current
timestamp at regular intervals as a way of informing other replicas regarding its leadership.

Taint & tolerance in Kubernetes:-

Taint – It is opposite they allow a node to replica set of PODS.

Toleration: - It applies to PODS. It allows the scheduler to schedule pods with matching taints.

NODE AFFINITY: - It is a property of PODS to attracts them to set of NODES (Either as a preference or
hard requirement)

Node Scheduler: - It is control plane process which assigns PODS to NODES. It determines which NODES
are valid placement for each PODS in the scheduling queue according to the constraints and available
resources. Scheduler then ranks each valid NODE and binds the PODS to a suitable NODE.

NODE SELCTOR: - The simplest recommended form of NODE selection constraints. You can add NODE
selector field to your POD specification and specify the NODE labels you want to target NODE to have.
Kubernetes only schedule PODS in to NODES that have each of the labels you specify.

NODE ANTI- AFFINITY: - It is also called inter POD- Affinity allows you to constraints PODS against labels
on other pods.

ROUTERS on KUBERNETES: - IT is a turnkey for K8s networking with aim to provide operation simplicity.
Networking is hard as such. In typical K8S cluster you would need to install multiple networks from
components for various functionality.

Secrets in K8s :- Secret is a Object that contains a small amount of sensitive data such as password , A
token or KEY. –-- Kubectl ----Use a configuration file --- Use the Kustomize tool.

Workloads in K8S :- It is an application running in K8s. It is a single component or several that works
together run on K8s you run in it inside a POD

You might also like