Find Interview Questions for Deltax

A kubelet is an agent that runs on each node in a Kubernetes cluster. Its role is to manage the containers on that node, ensuring they are running as specified in the Pod specifications, monitoring their health, and reporting back to the Kubernetes control plane.

You can expose a Kubernetes application to the outside world by using a Service of type LoadBalancer, NodePort, or Ingress.

The main components of the Kubernetes architecture are:

1. **Master Node**: Manages the Kubernetes cluster and includes components like the API server, etcd, controller manager, and scheduler.
2. **Worker Nodes**: Run the applications and contain components like the kubelet, kube-proxy, and container runtime.
3. **etcd**: A distributed key-value store for storing cluster data.
4. **API Server**: The front-end for the Kubernetes control plane, handling requests and communication.
5. **Controller Manager**: Manages controllers that regulate the state of the cluster.
6. **Scheduler**: Assigns workloads to worker nodes based on resource availability.
7. **Kubelet**: An agent that runs on each worker node, ensuring containers are running in pods.
8. **Kube-proxy**: Manages network routing for services in the cluster.

A Service in Kubernetes is an abstraction that defines a logical set of Pods and a policy to access them. It enables communication between different components in a Kubernetes cluster.

The types of Services available in Kubernetes are:

1. **ClusterIP**: Exposes the Service on a cluster-internal IP. It is only accessible from within the cluster.
2. **NodePort**: Exposes the Service on each Node’s IP at a static port. It allows external access to the Service.
3. **LoadBalancer**: Creates an external load balancer in supported cloud providers, routing traffic to the NodePort.
4. **ExternalName**: Maps the Service to the contents of the externalName field (e.g., a DNS name), allowing access to external services.

You can perform scaling in Kubernetes using the `kubectl scale` command to adjust the number of replicas in a deployment, or by configuring the Horizontal Pod Autoscaler (HPA) to automatically scale the number of pods based on resource usage metrics.

A commit in Git is a snapshot of changes made to the files in a repository. It contains the modified files, a unique identifier (hash), the author's information, a timestamp, and a commit message describing the changes.

.gitignore is a file used in Git to specify which files or directories should be ignored by version control. It prevents certain files, like temporary files or sensitive information, from being tracked and included in commits.

– **git add**: Stages changes in your working directory for the next commit.
– **git commit**: Records the staged changes in the repository's history with a message.
– **git push**: Uploads your local commits to a remote repository.

A detached HEAD in Git occurs when the HEAD pointer is not pointing to a branch, but directly to a specific commit. This means you are not on a branch, and any new commits will not be associated with any branch until you create a new branch or switch back to an existing one.

To initialize a new Git repository, use the command:

“`
git init
“`