Keep an app running with Kubernetes — EKS and Kubernetes

Your goal

Plan how a Kubernetes app keeps the right number of healthy copies running.

Why this matters

Your team already uses Kubernetes. You will separate the managed control system from app workers, describe the app’s desired state, and route traffic to healthy copies.

Words you will use

Kubernetes manages container workloads. A pod runs one or more containers. A Deployment describes desired app copies. A Service gives pods a stable way to be reached.

How to proceed

Read each situation and choose an answer. The lesson explains the result. Try again if needed, then continue through all three decisions and finish the tour.

1. Divide the responsibilities

Your team wants AWS to manage the Kubernetes control plane. The app still needs suitable compute, permissions, and configuration. Choose the accurate expectation.

What does EKS provide?

A managed Kubernetes control plane with compute options.

EKS manages the control plane. Your responsibilities for workers vary with the compute option, and you still own app settings, access, and behavior. Managed infrastructure does not make every workload healthy.

The team understands what it must still manage.

Managed control plane + chosen compute + your workload

2. Describe the desired state

A pod may fail or a worker may be replaced. You want Kubernetes to work toward three healthy copies of your web app. Choose what to declare.

What should describe the app?

A Deployment with replicas and health checks.

A Deployment describes the desired app state. Kubernetes can replace pods to move toward it, provided resources and settings allow. Health checks help distinguish a started process from an app ready for traffic.

The app has a repeatable desired state.

Deployment → desired replicas + health checks

3. Reach changing pods

Replacement pods can have different addresses. Clients need a stable way to reach ready app copies rather than saving each pod IP. Choose the next component.

What should clients use?

A Kubernetes Service selecting the app’s ready pods.

A Service provides a stable access point for a set of pods. Exposure outside the cluster needs an appropriate additional setup. Stable routing and healthy pods are both needed for a usable app.

Clients have a stable route to changing app copies.

Client → Service → ready app pod

Practice, then check your understanding

In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.

Read the official AWS documentation for service behavior and production details.