Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create a Secret:
- Create a secret containing the usemame and password required to access the private registry.
- Replace 'your-registry-username' and 'your-registry-password' with your actual credentials.

2. Update the Deployment - Modify the Deployment configuration to include the 'imagePullSecrets' field. - Add the name oftne secret you created in the previous step. - Replace 'your-private-registry-domain/your-database-image:your-version' with the actual image name and version.

3. Apply the Changes: - Apply the updated Deployment configuration using 'kubectl apply -f my-app-deployment.yamr. 4. Verify the Pull: - Check the logs of the Pods in the Deployment. You should see messages indicating that the database image is pulled from the private registry using the provided credentials.

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Define the Pod YAML: Create a Pod YAML file that includes the web server, database, and proxy containers.

2. Configure the Proxy Container: Choose a suitable proxy container image (e.g., Nginx, HAProxy) and configure it to forward requests from port 8080 to the database container on port 5432 3. Implement Logging: Configure the proxy container to log incoming requests to the '/var/log/proxy' directory. You can use the proxy container's built- in logging facilities or install a separate logging agent within the container. 4. Deploy the Pod: Apply the Pod YAML using ' kubectl apply -f my-app-pod_yaml' 5. Verify Functionality: Access the web server container on port 80 and ensure requests are forwarded to the database container Check the log file ' Ivar/log/proxys to verify that requests are being logged. Note: This solution demonstrates using a proxy container to manage communication between different containers within a Pod. You can customize the proxy's configuration based on your specific application's requirements.,

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Update the Deployment YAML:
- Update the 'replicas to 2_
- Define 'maxunavailable: 1 ' and 'maxSurge: 1 ' in the 'strategy.rollingupdate' section to control the rolling update process.
- Configure a 'strategy-type' to 'Rollingupdate' to trigger a rolling update when the deployment is updated.
- Add a 'spec-template.spec.imagePullPolicy: Always' to ensure that the new image is pulled even if it exists in the pod's local cache.

2. Create the Deployment: - Apply the updated YAML file using 'kubectl apply -f redis-deployment.yaml' 3. Verify the Deployment - Check the status of the deployment using 'kubectl get deployments redis-deployment' to confirm the rollout and updated replica count. 4. Trigger the Automatic Update. - Push a new image to the Docker Hub repository 5. Monitor the Deployment: - Use 'kubectl get pods -l app=rediS to monitor the pod updates during the rolling update process. You will observe that one new pod with the updated image is created, and then one old pod is terminated- This ensures that there is no downtime during the update process. 6. Check for Successful Update: - Once the deployment is complete, use 'kubectl describe deployment redis-deployment' to see that the 'updatedReplicaS field matches the 'replicas' field, indicating a successful update.

Correct Answer:

See the Explanation below for complete solution.
Explanation:
Below are the exact steps/commands you can run.
1) Locate the Deployment and its namespace
kubectl get deploy -A | grep nginx-resources
You should see output like:
<namespace> nginx-resources ...
Set a variable (replace <NS> with what you see):
NS=<NS>
Confirm replicas:
kubectl -n $NS get deploy nginx-resources -o jsonpath='{.spec.replicas}{"\n"}'
2) Check if there is a ResourceQuota in that namespace
kubectl -n $NS get resourcequota
kubectl -n $NS describe resourcequota
If there is a quota, note these fields (common ones):
* requests.cpu
* requests.memory
* limits.cpu
* limits.memory
3) Decide requests/limits for the Deployment (example values)
If the question (in your environment) provides specific values, use those.
If it doesn't, a typical safe pair is:
* requests: cpu: 100m, memory: 128Mi
* limits: cpu: 200m, memory: 256Mi
I'll proceed with these example values. If your lab specifies different numbers, just swap them in.
4) Update the existing Deployment (DO NOT DELETE)
Option A (fastest): kubectl set resources
Assuming the container name is the first container (we'll detect it):
kubectl -n $NS get deploy nginx-resources -o jsonpath='{.spec.template.spec.containers[*].name}{"\n"}' If it prints a single container name, set it like this:
kubectl -n $NS set resources deploy nginx-resources \
--requests=cpu=100m,memory=128Mi \
--limits=cpu=200m,memory=256Mi
Verify the Deployment now has resources
kubectl -n $NS get deploy nginx-resources -o jsonpath='{.spec.template.spec.containers[0].resources}{"\n"}'
5) Compute the total resources requested by the Deployment
Get replicas:
REPLICAS=$(kubectl -n $NS get deploy nginx-resources -o jsonpath='{.spec.replicas}') echo $REPLICAS
6) Ensure the namespace quota matches (or exceeds) those totals
This is the part the question warns about: if the quota is too low, the Deployment update will fail to roll out.
6.1 If a ResourceQuota already exists
Patch it to allow at least the totals you calculated.
First, identify quota name:
RQ=$(kubectl -n $NS get resourcequota -o jsonpath='{.items[0].metadata.name}') echo $RQ Then patch (example: replicas=2 # requests.cpu=200m, requests.memory=256Mi):
kubectl -n $NS patch resourcequota $RQ --type='merge' -p '{
"spec": {
"hard": {
"requests.cpu": "200m",
"requests.memory": "256Mi",
"limits.cpu": "400m",
"limits.memory": "512Mi"
}
}
}'
Adjust those numbers to your replicas × request, and replicas × limit (if your quota also enforces limits).
6.2 If there is NO ResourceQuota
Create one that matches the Deployment max request totals.
Example for replicas=2 with our sample requests/limits:
cat <<EOF | kubectl apply -n $NS -f -
apiVersion: v1
kind: ResourceQuota
metadata:
name: nginx-resources-quota
spec:
hard:
requests.cpu: "200m"
requests.memory: "256Mi"
limits.cpu: "400m"
limits.memory: "512Mi"
EOF
7) Verify rollout succeeds
kubectl -n $NS rollout status deploy nginx-resources
kubectl -n $NS get pods
Verify the running pods actually have the requests/limits:
kubectl -n $NS get pod -l app=nginx-resources -o jsonpath='{range .items[*]}{.metadata.name}{" "}{.spec.
containers[0].resources}{"\n"}{end}'
(If the label selector app=nginx-resources doesn't exist, just pick a pod name from kubectl get pods and run:) kubectl -n $NS describe pod <pod-name> | sed -n '/Limits:/,/Requests:/p' Common reasons this fails (and the fix)
* Rollout stuck / pods pending with "exceeded quota"Check:
* kubectl -n $NS describe pod <pending-pod>
* kubectl -n $NS describe resourcequota
Fix: increase ResourceQuota hard values to match required totals.
* You set requests higher than quota allowsFix: either reduce requests or raise quota.
kubectl get deploy -A | grep nginx-resources
kubectl -n <NS> get deploy nginx-resources -o jsonpath='{.spec.replicas}{"\n"}{.spec.template.spec.
containers[0].name}{"\n"}'
kubectl -n <NS> describe resourcequota

Correct Answer:

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Create a Role:
- Create a YAML file named 'scale-app-role.yaml' with the following content:

2. Create a RoleBinding: - Create a YAML file named 'scale-app-rolebinding.yaml' with the following content:

3. Apply the configuration: - Apply the Role and Role8inding using the following commands: bash kubectl apply -f scale-app-role.yaml kubectl apply -f scale-app-rolebinding-yaml 4. Verify the configuration: - You can verify the configuration by using the following command: bash kubectl auth can-i --list --as=user:testuser--group-developers--namespace-dev - Replace 'testuser' with the name of a user in the 'developers' group. The output should show only the following permissions: - 'apps/deployments': 'get, "list, 'watch', 'update', 'patch', 'scale' 5. Test the permissions: - Try to scale the Sapp-deployment deployment using the 'kubectr command as a user in the 'developers group. - Try to perform other actions on the deployment or other resources in the 'devs namespace. You should only be able to scale the Sapp-deployment deployment.