What you will learn
- Explain what scale and roll back a Deployment accomplishes in Kubernetes.
- Use the demonstrated command or workspace procedure to practise scale and roll back a Deployment.
- Compare the visible output with your own training result and identify a likely failure.
Scale and roll back a Deployment
You are responsible for a test cluster running a small web service and a background worker. The subject is scale and roll back a Deployment. A dry-run produces a Deployment manifest rather than creating anything in the cluster. Practise scale and roll back a Deployment in a training environment, not by experimenting on a team’s live system. Read the command or UI step carefully: its target, options and access permissions matter. Compare the visible result with the stated goal and identify what would be different if the input were missing, a setting were invalid, or access were denied. Keep the result as your evidence.
- What matters: A dry-run produces a Deployment manifest rather than creating anything in the cluster.
- Practical syntax: In the example, kubectl create deployment etg-web --image=nginx:alpine --dry-run=client -o yaml is the first operation to understand. Read its flags and the context it targets.
- What to look for: For scale and roll back a deployment, inspect the result shown immediately after Example 1 and compare it with your practice run.
- Avoid a real-world mistake: While practising scale and roll back a deployment, follow this caution: The currently selected context can point to production; inspect context and namespace before every action.
Technical vocabulary
Scale and roll back a Deployment
A dry-run produces a Deployment manifest rather than creating anything in the cluster.
Command
The tool instruction for this topic begins with kubectl create deployment etg-web --image=nginx:alpine --dry-run=client -o yaml. Read its target and options before using it.
Result
For scale and roll back a Deployment, the example result is: apiVersion: apps/v1 kind: Deployment. Actual remote-service output depends on your environment.
Examples
Use scale and roll back a deployment
kubectl create deployment etg-web --image=nginx:alpine --dry-run=client -o yamlapiVersion: apps/v1 kind: Deployment
Explanation: A dry-run produces a Deployment manifest rather than creating anything in the cluster.
Inspect the working context
kubectl config current-contextkind-etg-lab
Explanation: Confirm that this action will use the intended test workload. The value shown is an illustration, so compare your actual response.
Investigate a problem
kubectl get events -A --sort-by=.lastTimestamp(recent warning and normal cluster events)
Explanation: Use this separate diagnostic command when checking scale and roll back a deployment. Interpret warnings and missing permissions before changing anything.
Practise and build
Try it: Scale and roll back a Deployment
Repeat Example 1 for scale and roll back a Deployment in a permitted lab. Change one safe input or setting, then record the real result rather than copying the sample Output above.
Check your approach
A dry-run produces a Deployment manifest rather than creating anything in the cluster. If the result differs, first inspect the active account or workspace and review your command or action.
Find the issue
Imagine that your test workload is not in the expected state after this exercise. Identify the missing prerequisite or permission and write a safe diagnostic procedure.
Show a possible resolution
The currently selected context can point to production; inspect context and namespace before every action. Use the separate diagnostic example to gather evidence before applying a change.
Level project: Run a test service in a local cluster
Use scale and roll back a Deployment as a specific component of the project. Document the feature, why it belongs in the workflow, the steps taken and the verified state. Keep the result in your private learner portfolio.
Questions
01What does scale and roll back a Deployment help you accomplish?
A dry-run produces a Deployment manifest rather than creating anything in the cluster.
02What action starts the scale and roll back a Deployment demonstration?
kubectl create deployment etg-web --image=nginx:alpine --dry-run=client -o yaml
03What does the first Output tell you about scale and roll back a Deployment?
The illustrated result is apiVersion: apps/v1 kind: Deployment; your environment may display other identifiers, counts or status information.
04What should you check if scale and roll back a Deployment does not behave as shown?
The currently selected context can point to production; inspect context and namespace before every action.
Summary
A dry-run produces a Deployment manifest rather than creating anything in the cluster. You can now connect this feature to your level project. Before moving to Understand labels selectors and annotations, make sure the primary demonstration works or that you can explain precisely why it did not work in your chosen environment.