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: 0' 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.
- Set 'spec.template.spec.containers[0].restartPolicy: Always' to ensure the database container restarts automatically when it encounters a failure.

2. Create the Deployment: - Apply the updated YAML file using 'kubectl apply -f database-deployment.yaml' 3. Verify the Deployment: - Check the status of the deployment using 'kubectl get deployments database-deployment' to confirm the rollout and updated replica count. 4. Test the Restart Policy: - Trigger a failure in the 'database' container within one of the pods. This can be done by sending a SIGKILL signal to the container or by simulating a crash within the container itself. - Observe that the 'database' container will be restarted automatically while other containers in the same pod will remain unaffected. 5. Trigger the Automatic Update: - Push a new image to the 'my-database-image:latest registry. 6. Monitor the Deployment: - Use "kubectl get pods -l app=database' to monitor the pod updates during the rolling update process. 7. Check for Successful Update: - Once the deployment is complete, use 'kubectl describe deployment database-deployment' to see that the 'updatedReplicas' field matches the 'replicas' field, indicating a successful update.

See the solution below with Step by Step Explanation.
Explanation:
Solution (Step by Step) :
1. Update the ConfigMap:
- Modify the 'db-config' ConfigMap to include the new connection string. This can be done using 'kubectl patch' or 'kubectl edit' commands. For instance, using 'kubectl patch':
kubectl patch configmap db-config -p '{"data": {"db-connection-string": "new-connection-string"}}'
2. Verify the Updated ConfigMap:
- Confirm the changes were applied to the ConfigMap by checking its data with 'kubectl get configmap db- config -o yaml':
kubectl get configmap db-config -o yaml
This should show the updated 'db-connection-string' value.
3. Observe the Pods:
- Monitor the pods in the 'web-app' Deployment. Since ConfigMaps are mounted as volumes, the updated connection string will automatically be available to the pods without any manual restarts. You can check the pods using get pods -l app=web-app'.
kubectl get pods -l app=web-app
4. Confirm Application Functionality:
- Verify that the web application is now using the updated database connection by performing relevant actions within the application, such as querying data or performing other operations.

kubectl get nodes --show-labels