UPDATES

Question Context: ఈ cluster ని kubeadm తో setup చేశారు. ఇప్పుడు ఈ cluster ని ఒక కొత్త machine కి migrate చేశారు. Migration సమయంలో కొన్ని cluster components break అయ్యాయి.వాటిని fix చేసి cluster మళ్ళీ run అయ్యేలా చేయాలి. ఒకే ఒక్క node ఉన్న cluster AWNS: ee file lo Vi /etc/kubernetes/manifests/kube-apiserver.yaml ee file lo ETCD ip address wrong ga undi https://127.0.0.1:2379 Ila undali akkada 128 undi okkosari portnumber kuda change chestaru gurthupettukovali port number ku

AWNS: Note: Flannel is not support for network policy enforcement So go for Calico Now Check the node Communication status Ckeck if any cni installed # kubectl get pods -A | grep -E "flannel|calico" Install tigera operator and verify kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.29.3/manifests/tigera-operator.yaml # 3) Install the Calico custom resources (the actual Calico installation config) kubectl apply -f https://raw.githubusercontent.com/p

Question 15: An NGINX Deployment named nginx-static is running in the nginx-static namesapce. it is configured using a ConfigMap named nginx-config. Update the nginx-config ConfigMap to allow only TLSv1.3 connection You may re-create, restart, or scale resources as necessary. You can use the folowing command to test the changes. #curl --tls-max 1.3 https://web.k8s.local #curl --tls-max 1.2 https://web.k8s.local #shouldn't be open ==============================================

Question 14: Verify the cert-manager application which has been deployed to your cluster. using kubectl create a list of all cert-manager Custom Resource Definitions(CRDs) and save it to ~/resources.yaml you must be kubectl's default output format Do not set an output format. Using kubectl, extract the documentation for subject specification field of the certificate custom Resource and save it to ~/subject.yaml ==================================================== Answer: #kub

Question 12: First create a gateway named web-gateway with hostname gateway.web.k8s.local that maintain the existing TLS and listener configuration from the existing ingress resource named web. Next , create an HTTPRoute named web-route with hostname gateway.web.k8s.local that maintains the existing routing rules from the current ingress resource named web. You can test your Gateway API configuration with the following command: curl https://gateway.web.k8s.local finaly

Question - 11: Create a PersistentVolumeClaim (PVC) named mariadb in the mariadb namespace with the following specifications Access Mode: ReadWriteOnce Size: 250mi There is only one existing PersistentVolume Edit the MariaDB Deployment file located at ~/mariadb-deployment.yaml to use PVC you created in the previous step. ============================================================= Answer: 1- Nevigate kubernetes URL then then search PersistentVolumeClaim https://kubernetes

Question 9: Create a new PriorityClass named high-priority for user-workloads with a volume that is one less class than the highest existing user-defined priority class value. Patch the existing Deployment busybox-logger running in the priority namespace to use the high-priority priority class. Ensure that the busybox-logger deployment rolls out successfully with the new priority class set. It is expected that Pods from other Deployments running in the priority namespace are

Question - 8: Reconfigure the existing Deployment front-end in namespace spline-reticulator to expose port 80/tcp of the existing container nginx. Create a new service named front-end-svc exposing the container port80/tcp Configure the new service to also expose the indivisual Pods via a NodePort ======================================================= Answer: We will have to modify deployment only # kubectl edit deployment front-end -n spline-reticulator navigate to :...

Question 7: 1-First create a new StorageClasss named local-path for an existing provisioner named rancher.io/local-path. 2-Set volume binding mode to: WaitFroFirstCustomer 3-Not setting the volume binding mode or setting it to anything other than WaitFroFirstCustomer may result in a reduced score. 4-Next configure the StorageClass local-path as the default StorageClass. 5-Do not modify any existing Deployment or PersistentVolumeClaims. Failure to do so may result in a reduced

Question 4: All WorldPress Application in the relative-fawn namespace consist of: ⦁ A wordPress Deployment with 3 replicas Adjust all pod resource requests as follow: Devide node resources evenly across all 3 Pods. ⦁ Give each Pod a fair share of CPU and memory. ⦁ Add enough overhead to keep the node stable. Use the exact some requests for both containers and init containers. You are not required to change any resource limits. It may help to temporarily scale the WordPress De

Question 13: Review and apply the appropriate N/W policy from the provided YAML samples. Ensure that the chosen NetworkPolicy is not overly permissive, but allows communication between the frontend and backend Deployments, which run in the frontend and backend namespaces respectively. First analyze the frontend and backend Departments to determine the specific requirements for the NetworkPolicy that needs to be applied. Next, examine the Network Policy YAML samples located in

Question 6: Install and set up a Container Network Interface (CNI) that meets these requirement: Pick and install one of these CNI option: Flanel version 0.26.7 manifiest: https://github.com/flannel-io/flannel/releases/latest/download/kubeflannel.yml https://github.com/flannel-io/flannel/releases/download/v0.26.7/kube-flannel.yml Calico Version 3.29.3: https://docs.tigera.io/calico/latest/getting-started/kubernetes/self-managed-onprem/onpremises?utm_source Manifest:...

KUBERNETES INSTALLATION ON CENTOS-8 ----------------------------------- Prerequisites: -------------- It is recommended that your nodes...