Answer-first summary for fast verification
Answer: Not updating the Docker image tag to a new version.
The application's configuration is still referencing the original EKS cluster because the developer did not update the Docker image tag to a new version. When changes are made to the configuration, it is crucial to update the Docker image tag to ensure the application deployment reflects the new configuration. Without updating the tag, the deployment uses the old image with the previous configuration settings, which causes the application to still connect to the old backend.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A developer migrates an app to Amazon EKS, using Amazon ECR, and updates it to a new AWS account with backend changes. Despite successful Docker image build and pipeline deployment, the app still connects to the old backend. The issue is identified as the app's configuration still pointing to the original EKS cluster. What could be the reason for the app not connecting to the new backend resources?
A
Failure to create a new AWS account.
B
Adding a new tag to the Docker image.
C
Not updating the Docker image tag to a new version.
D
Pushing changes to a new Docker image tag.
No comments yet.