Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,551,790
Community Members
 
Community Events
184
Community Groups

Example blue/green CI/CD with Bitbucket Pipelines to AWS EKS

Monica Gordillo
Monica Gordillo Jul 21, 2021

I'm looking for an example blue/green deployment pipeline to AWS EKS.  I found a link for a basic "Deploy to Kubernetes" setup.  https://support.atlassian.com/bitbucket-cloud/docs/deploy-to-kubernetes/

I'm looking for either a blue/green deployment or canary deployment example. 

Answer
Watch
Like # people like this
551 views

1 answer

0 votes
etiennej
etiennej
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
Apr 04, 2023

Similarly looking for an example blue/green deployment pipeline but instead for AWS Elastic Beanstalk... My balanced solution is just have two deploy steps, both trigger:manual, and I can manually go through and decide which gets updated. Will have to think through further

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

See all events