Kubernetes agents in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Kubernetes Agent Pod Templates in Jenkins

In Jenkins, when configuring a Kubernetes agent pod template, which of the following best describes the purpose of the containers section inside the pod template?

A It configures the network policies for the Kubernetes cluster.

B It specifies the Jenkins master node's container image for running builds.

C It lists all the Kubernetes nodes available for scheduling pods.

D It defines the containers that will run inside the agent pod, specifying their images and commands.

💡 Hint

Think about what runs inside the agent pod that Jenkins uses to execute jobs.

The containers section defines the containers inside the Kubernetes pod that Jenkins uses as agents. These containers run the build steps.

💻 Command Output

intermediate

Output of Jenkins Kubernetes Agent Pod Creation

Given the following Jenkins pipeline snippet that uses a Kubernetes agent:

pipeline {
  agent {
    kubernetes {
      yaml '''
apiVersion: v1
kind: Pod
spec:
  containers:
  - name: jnlp
    image: jenkins/inbound-agent:latest
'''
    }
  }
  stages {
    stage('Test') {
      steps {
        sh 'echo Hello from Kubernetes agent'
      }
    }
  }
}

What will be the output of the sh step when this pipeline runs?

A Permission denied

B Error: No such file or directory

C Hello from Kubernetes agent

D Pipeline failed to start agent pod

💡 Hint

The sh step runs inside the container defined in the pod template.

The sh step executes the echo command inside the Kubernetes agent pod container, so it outputs the string as expected.

❓ Troubleshoot

advanced

Troubleshooting Kubernetes Agent Pod Scheduling Failure

A Jenkins pipeline configured with a Kubernetes agent pod template fails to start the agent pod. The Jenkins logs show the error: Failed to schedule pod: insufficient cpu. What is the most likely cause?

A The Kubernetes cluster does not have enough CPU resources available to schedule the pod.

B The Jenkins master node is offline.

C The Jenkins agent container image is missing.

D The pod template YAML syntax is invalid.

💡 Hint

Consider what 'insufficient cpu' means in Kubernetes scheduling.

The error indicates the Kubernetes scheduler cannot find a node with enough CPU resources to run the pod, causing scheduling failure.

🔀 Workflow

advanced

Jenkins Kubernetes Agent Pod Lifecycle

Which sequence correctly describes the lifecycle of a Jenkins Kubernetes agent pod during a pipeline run?

A Jenkins master requests pod → Kubernetes schedules pod → Pod starts → Pipeline runs → Pod deleted

B Pipeline runs → Jenkins master requests pod → Pod deleted → Kubernetes schedules pod → Pod starts

C Pod deleted → Jenkins master requests pod → Pipeline runs → Kubernetes schedules pod → Pod starts

D Kubernetes schedules pod → Pod starts → Jenkins master requests pod → Pipeline runs → Pod deleted

💡 Hint

Think about the order from pod request to pod deletion after job completion.

The Jenkins master requests the pod, Kubernetes schedules and starts it, the pipeline runs inside, then the pod is deleted after completion.

✅ Best Practice

expert

Best Practice for Securing Jenkins Kubernetes Agents

Which of the following is the best practice to enhance security when running Jenkins agents as Kubernetes pods?

A Disable Kubernetes network policies to ensure agents can communicate freely.

B Run agent containers with the least privilege by setting a non-root user and restricting capabilities.

C Allow agents to run as root to avoid permission issues during builds.

D Use the default Jenkins inbound agent image without modifications for simplicity.

💡 Hint

Consider the principle of least privilege in container security.

Running containers as non-root users with restricted capabilities reduces security risks and limits damage if compromised.