Using Argo Rollouts with stateful services

Example with Argo Rollouts with two services that use a queue (RabbitMQ in our case). We want to do a blue/green deployment without affecting the production queue.

Local development

This is the workflow when you need to change the source code.

Run RabbitMQ locally

Install Docker

docker run --name some-rabbit -p 5672:5672 -p 5673:5673 -p 15672:15672 rabbitmq:3-management

You can visit the dashboard at http://localhost:15672. Username and password are guest:guest

Run the worker manually

Install GoLang locally

cd source/worker
APP_VERSION=1.2  go run .

You can now access the worker at http://localhost:8080

Click the button to test RabbitMQ connection - the worker sends messages to itself

Run the tester/producer locally

cd source/tester
go run .

You can now access the producer at http://localhost:7000

Click the Production button to send messages to the worker

Run all services at the same time

Install Docker compose (no need for local GoLang installation)

cd src
docker compose up

And now you can use

• http://localhost:15672 for RabbitMQ
• http://localhost:8000 for Stable worker
• http://localhost:9000 for Preview Worker

Deploy on Kubernetes

cd manifests/stateful-rollout
kubectl apply -f . 
kubectl port-forward svc/rabbitmq 15672:15672
kubectl port-forward svc/rabbitmq 5672:5672
kubectl port-forward svc/worker-active 8000:8080 
kubectl port-forward svc/worker-preview 9000:8080 for preview worker

And now you can use

• http://localhost:15672 for RabbitMQ
• http://localhost:8000 for Stable worker
• http://localhost:9000 for preview worker

Start a rollout

To see what the rollout is doing

kubectl-argo-rollouts get rollout my-worker 

Edit the file worker.yml and update the env version at line 43 to 2.0. Save the file and re-apply with kubectl

Promote the rollout when ready with

kubectl-argo-rollouts promote my-worker