You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello community, I have setup bitbucket-pipelines for auto deployment to my AWS EKS cluster, below is the pipeline;
- step:
name: "Apply Billing App Latest Version"
services:
- docker
script:
- pipe: atlassian/aws-eks-kubectl-run:2.2.0
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: aws-region
CLUSTER_NAME: 'My-Cluster-Name'
KUBECTL_COMMAND: 'apply'
RESOURCE_PATH: 'infra/k8s/billing-dep.yaml'
KUBECTL_APPLY_ARGS: '-f'
Now, the problem is when Devs pushes their code to the bitbucket in a specific branch, the pipeline starts and build a docker image, then pushes the image to the AWS ECR, and then comes the deployment on EKS cluster, here I face the issue, the pipeline does not apply the latest docker image, I dont know why?
@Asad hi , Thanks for your question.
You docker image is set in your
infra/k8s/billing-dep.yaml
file, is this true?
`the pipeline starts and build a docker image, then pushes the image to the AWS ECR` -- maybe instead of latest tag provide some custom tag (exact version of latest image) ? And than update your yaml deployment file with new correct docker image version
Regards, Igor
for now, what I am doing, I just delete the old deployment using pipeline and apply new one and I know this is not the best.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.