Creating Pods with kubectl in Kubernetes - Practice Exercises

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of creating a pod with a missing image field?

You run the command kubectl run mypod --restart=Never --image= with an empty image value. What will kubectl output?

Kubernetes

kubectl run mypod --restart=Never --image=

A error: required flag(s) "image" not set

B pod/mypod created

C Warning: image field is empty, pod created but will fail to start

D command not found

💡 Hint

The image field is mandatory when creating a pod with kubectl run.

The --image flag is required to specify the container image. Leaving it empty causes kubectl to error out.

❓ Configuration

intermediate

Which YAML snippet correctly defines a pod with one container named 'web' running nginx?

Select the correct YAML configuration for a pod named 'web-pod' with a single container named 'web' using the nginx image.

A

apiVersion: v1
kind: Pod
metadata:
  name: web-pod
spec:
  containers:
  - web
  - image: nginx

B

apiVersion: v1
kind: Pod
metadata:
  name: web-pod
spec:
  containers:
    name: web
    image: nginx

C

apiVersion: v1
kind: Pod
metadata:
  name: web-pod
spec:
  containers:
  - name: web
    image: nginx

D

apiVersion: v1
kind: Pod
metadata:
  name: web-pod
spec:
  container:
  - name: web
    image: nginx

💡 Hint

The containers field must be a list with each container having a name and image.

Option C correctly uses the containers list with a container object having name and image fields.

🔀 Workflow

advanced

What is the correct sequence to create a pod from a YAML file and verify it is running?

Arrange the steps in the correct order to create a pod from a YAML file named pod.yaml and check its status.

A 1,2,4,3

B 1,2,3,4

C 1,3,2,4

D 2,1,3,4

💡 Hint

First create, then list, then inspect, then optionally delete.

The correct workflow is to apply the YAML, check pods, describe the pod for details, and delete if needed.

❓ Troubleshoot

advanced

What error will occur if you try to create a pod with an invalid apiVersion?

You use this YAML snippet to create a pod but the apiVersion is set to 'v2': apiVersion: v2 kind: Pod metadata: name: test-pod spec: containers: - name: test image: busybox command: ['sleep', '3600'] What error will kubectl show?

A error: unable to recognize "pod.yaml": no matches for kind "Pod" in version "v2"

B pod/test-pod created

C error: unknown flag: --apiVersion

D Warning: apiVersion v2 deprecated, pod created with warnings

💡 Hint

apiVersion must be a valid Kubernetes API version.

Using an invalid apiVersion causes kubectl to fail recognizing the resource kind.

✅ Best Practice

expert

Which kubectl command correctly creates a pod named 'fast-pod' with the image 'nginx' and disables restart policy?

Choose the command that creates a pod named 'fast-pod' using the nginx image and ensures the pod will not restart automatically.

A kubectl create pod fast-pod --image=nginx --restart=Always

B kubectl create pod fast-pod --image=nginx --restart=Never

C kubectl run fast-pod --image=nginx --restart=Always

D kubectl run fast-pod --image=nginx --restart=Never

💡 Hint

The restart policy 'Never' disables automatic pod restarts.

The kubectl run command with --restart=Never creates a pod that does not restart automatically.