Get The Important Preparation Guide With CKA Dumps [Q39-Q63]

Erhalten Sie den wichtigen Vorbereitungsleitfaden mit CKA Dumps [Q39-Q63]

ExamBoosts Januar 16, 2024 CKA > Linux-Stiftung 0

Diesen Beitrag bewerten

Get The Important Preparation Guide With CKA Dumps

Get Totally Free Updates on CKA Dumps PDF Questions

FRAGE 39
Create a nginx pod that will be deployed to node with the label
“gpu=true”

kubectl run nginx –image=nginx –restart=Always –dry-run -o
yaml > nodeselector-pod.yaml
// add the nodeSelector like below and create the pod
kubectl apply -f nodeselector-pod.yaml
vim nodeselector-pod.yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
nodeSelector:
gpu: true
containers:
– image: nginx
name: nginx
restartPolicy: Always
kubectl apply -f nodeselector-pod.yaml
//Verify
kubectl get no -show-labels
kubectl get po
kubectl describe po nginx | grep Node-Selectors

kubectl run nginx –image=nginx –restart=Always –dry-run -o
yaml > nodeselector-pod.yaml
// add the nodeSelector like below and create the pod
kubectl apply -f nodeselector-pod.yaml
vim nodeselector-pod.yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
nodeSelector:
gpu: true
yaml
//Verify
kubectl get no -show-labels
kubectl get po
kubectl describe po nginx | grep Node-Selectors

FRAGE 40
Score: 7%

Aufgabe
Reconfigure the existing deployment front-end and add a port specification named http exposing port 80/tcp of the existing container nginx.
Create a new service named front-end-svc exposing the container port http.
Configure the new service to also expose the individual Pods via a NodePort on the nodes on which they are scheduled.

See the solution below.
Erläuterung
Lösung:
kubectl get deploy front-end
kubectl edit deploy front-end -o yaml
#port specification named http
#service.yaml
apiVersion: v1
kind: Service
metadata:
name: front-end-svc
labels:
app: nginx
spec:
ports:
– port: 80
protocol: tcp
name: http
selector:
app: nginx
type: NodePort
# kubectl create -f service.yaml
# kubectl get svc
# port specification named http
kubectl expose deployment front-end –name=front-end-svc –port=80 –tarport=80 –type=NodePort

FRAGE 41
Create an nginx pod with container Port 80 and it should only receive traffic only it checks the endpoint / on port 80 and verify and delete the pod.

kubectl run nginx –image=nginx –restart=Never –port=80 —
dry-run -o yaml > nginx-pod.yaml
// add the readinessProbe section and create
vim nginx-pod.yaml
run: nginx
name: nginx
spec:
containers:
– image: nginx
name: nginx
ports:
– containerPort: 60
readinessProbe:
httpGet:
path: /
port: 60
restartPolicy: Never
kubectl apply -f nginx-pod.yaml
// verify
kubectl describe pod nginx | grep -i readiness
kubectl delete po nginx

kubectl run nginx –image=nginx –restart=Never –port=80 —
dry-run -o yaml > nginx-pod.yaml
// add the readinessProbe section and create
vim nginx-pod.yaml
apiVersion: v1
kind: Pod
metadata:
labels:
run: nginx
name: nginx
spec:
containers:
– image: nginx
name: nginx
ports:
– containerPort: 80
readinessProbe:
httpGet:
path: /
port: 80
restartPolicy: Never
kubectl apply -f nginx-pod.yaml
// verify
kubectl describe pod nginx | grep -i readiness
kubectl delete po nginx

FRAGE 42
Create a PersistentVolumeClaim of at least 3Gi storage and access mode ReadWriteOnce and verify status is Bound

vim task-pv-claim.yaml
apiVersion: v2
kind: PersistentVolumeClaim
metadata:
name: task-pv-claim
spec:
storageClassName: “”
accessModes:
– ReadWriteOnce
resources:
requests:
storage: 4Gi
kubectl apply -f task-pv-claim.yaml
//Verify
kubectl get pv
NAME CAPACITY ACCESS
MODES RECLAIM POLICY STATUS CLAIM
STORAGECLASS REASON AGE
task-pv-volume 4Gi RWO
Retain Bound default/task-pv-claim
6m16s
kubectl get pvc
NAME STATUS VOLUME
CAPACITY ACCESS MODES STORAGECLASS AGE
task-pv-claim Bound task-pv-volume
5Gi RWO 6s

vim task-pv-claim.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: task-pv-claim
spec:
storageClassName: “”
accessModes:
– ReadWriteOnce
resources:
requests:
storage: 3Gi
kubectl apply -f task-pv-claim.yaml
//Verify
kubectl get pv
NAME CAPACITY ACCESS
MODES RECLAIM POLICY STATUS CLAIM
STORAGECLASS REASON AGE
task-pv-volume 5Gi RWO
Retain Bound default/task-pv-claim
6m16s
kubectl get pvc
NAME STATUS VOLUME
CAPACITY ACCESS MODES STORAGECLASS AGE
task-pv-claim Bound task-pv-volume
5Gi RWO 6s

FRAGE 43
List “nginx-dev” and “nginx-prod” pod and delete those pods

See the solution below.
Erläuterung
kubect1 get pods -o wide
kubectl delete po “nginx-dev”kubectl delete po “nginx-prod”

FRAGE 44
A Kubernetes worker node, named wk8s-node-0 is in state NotReady. Investigate why this is the case, and perform any appropriate steps to bring the node to a Ready state, ensuring that any changes are made permanent.
You can ssh to the failed node using:
[student@node-1] $ | ssh Wk8s-node-0
You can assume elevated privileges on the node with the following command:
[student@w8ks-node-0] $ | sudo -i

See the solution below.
Erläuterung
solution

FRAGE 45
List all persistent volumes sorted by capacity, saving the full kubectl output to
/opt/KUCC00102/volume_list. Use kubectl ‘s own functionality for sorting the output, and do not manipulate it any further.

See the solution below.
Erläuterung
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\2 C.JPG

FRAGE 46
Create a pod that echo “hello world” and then exists. Have the pod deleted automatically when it’s completed

kubectl run busybox –image=busybox -it –rm –restart=Never — /bin/sh -c ‘echo hello world’ kubectl get po # You shouldn’t see pod with the name “busybox”

FRAGE 47
Create a pod that echo “hello world” and then exists. Have the pod deleted automatically when it’s completed

See the solution below.
Erläuterung
kubectl run busybox –image=busybox -it –rm –restart=Never —
/bin/sh -c ‘echo hello world’
kubectl get po # You shouldn’t see pod with the name “busybox”

FRAGE 48
List all persistent volumes sorted by capacity, saving the full kubectl output to /opt/KUCC00102/volume_list. Use kubectl ‘s own functionality for sorting the output, and do not manipulate it any further.

solution

FRAGE 49
Get the list of pods of webapp deployment

// Get the label of the deployment
kubectl get deploy –show-labels
kubectl get pods -l app=webapp

// Get the label of the deployment
kubectl get deploy –show-labels
// Get the pods with that label
kubectl get pods -l app=webapp

FRAGE 50
Score: 4%

Aufgabe
Create a persistent volume with name app-data , of capacity 1Gi and access mode ReadOnlyMany. The type of volume is hostPath and its location is /srv/app-data .

Lösung:
#vi pv.yaml
apiVersion: v1
kind: PersistentVolume
metadata:
name: app-config
spec:
capacity:
storage: 1Gi
accessModes:
– ReadOnlyMany
hostPath:
path: /srv/app-config
#
kubectl create -f pv.yaml

FRAGE 51
List all service account and create a service account called “admin”

kubectl get sa
kubectl get sa –all-namespaces
kubectl create sa admin
//Verify
kubectl get sa admin -o yaml

kubectl get sa
kubectl get sa –all-namespaces
//Verify
kubectl get sa admin -o yaml

FRAGE 52
Create a deployment as follows:
Name: nginx-random
Exposed via a service nginx-random
Ensure that the service & pod are accessible via their respective DNS records The container(s) within any pod(s) running as a part of this deployment should use the nginx Image Next, use the utility nslookup to look up the DNS records of the service & pod and write the output to
/opt/KUNW00601/service.dns and /opt/KUNW00601/pod.dns respectively.

See the solution below.
Erläuterung
Lösung:
F:\Work\Data Entry Work\Data Entry\20200827\CKA\17 C.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\17 D.JPG

F:\Work\Data Entry Work\Data Entry\20200827\CKA\17 E.JPG

FRAGE 53
Set the node named ek8s-node-1 as unavailable and reschedule all the pods running on it.

See the solution below.
Erläuterung
solution
F:\Work\Data Entry Work\Data Entry\20200827\CKA\19 B.JPG

FRAGE 54
Create a pod with environment variables as var1=value1.Check the environment variable in pod

kubectl run nginx –image=nginx –restart=Never –env=var1=value1
# then
kubectl exec -it nginx — env
# or
kubectl describe po nginx | grep value1

kubectl run nginx –image=nginx –restart=Never –env=var1=value1
# then
kubectl exec -it nginx — env
# or
kubectl exec -it nginx — sh -c ‘echo $var1’
# or
kubectl describe po nginx | grep value1

FRAGE 55
Create a pod with environment variables as var1=value1.Check the environment variable in pod

FRAGE 56
Task Weight: 4%

Aufgabe
Schedule a Pod as follows:
* Name: kucc1
* App Containers: 2
* Container Name/Images:
o nginx
o consul

Lösung:

FRAGE 57
Check the history of deployment

kubectl rollout history deployment webapp

FRAGE 58
Create 2 nginx image pods in which one of them is labelled with env=prod and another one labelled with env=dev and verify the same.

kubectl run –generator=run-pod/v1 –image=nginx — labels=env=prod nginx-prod –dry-run -o yaml > nginx-prodpod.yaml Now, edit nginx-prod-pod.yaml file and remove entries like “creationTimestamp: null” “dnsPolicy: ClusterFirst” vim nginx-prod-pod.yaml apiVersion: v1 kind: Pod metadata:
labels:
env: prod
name: nginx-prod
spec:
containers:
– image: nginx
name: nginx-prod
restartPolicy: Always
# kubectl create -f nginx-prod-pod.yaml
kubectl run –generator=run-pod/v1 –image=nginx —
labels=env=dev nginx-dev –dry-run -o yaml > nginx-dev-pod.yaml
apiVersion: v1
kind: Pod
metadata:
labels:
env: dev
name: nginx-dev
spec:
containers:
– image: nginx
name: nginx-dev
restartPolicy: Always
# kubectl create -f nginx-prod-dev.yaml
Verify :
kubectl get po –show-labels
kubectl get po -l env=prod
kubectl get po -l env=dev

FRAGE 59
Get IP address of the pod – “nginx-dev”

Kubect1 get po -o wide
Using JsonPath
kubect1 get pods -o=jsonpath='{range
.items[*]}{.metadata.name}{“\t”}{.status.podIP}{“\n”}{end}’

FRAGE 60
Check to see how many worker nodes are ready (not including nodes tainted NoSchedule) and write the number to /opt/KUCC00104/kucc00104.txt.

See the solution below.
Erläuterung
solution

FRAGE 61
Create a Kubernetes secret as follows:
Name: super-secret
password: bob
Create a pod named pod-secrets-via-file, using the redis Image, which mounts a secret named super-secret at /secrets.
Create a second pod named pod-secrets-via-env, using the redis Image, which exports password as CONFIDENTIAL

solution