title	author	slug
Canary Deploys with Waypoint and Consul	Nic Jackson, Erik Veld	consul_waypoint

Readme

• Gogs UI
• Waypoint UI
• Grafana
• Consul

Logging into Waypoint

Set the environment variables to use the Kubernetes config set by Shipyard

eval $(shipyard env)

Login to the Waypoint server

waypoint login --from-kubernetes localhost:9701

You can now open the Waypoint UI

waypoint ui -authenticate

Deploying the Payments application to Waypoint

The example application is located in ./files/payments, change into this folder and execute the following commands:

Build and deploy the application

waypoint up

Once complete the application will be deployed to Kubernetes, you can test it using the following command:

curl -vv http://localhost:18080/v1/weather

The application has simulated traffic sent through to it, full visualization can be seen in the Grafana dashboard:

http://localhost:8080/d/sdfsdfsdf/application-dashboard?orgId=1&refresh=10s

Manually deploying the canary release

• Make a change to the application

export GIT_SSL_NO_VERIFY=true
git clone https://localhost:3000/hashicraft/payments.git

• Add a service resolver to consul (CRD)

kubectl apply -f ./files/k8s_config/consul/service-resolver.yaml

• Add a service splitter to consul (CRD)

kubectl apply -f ./files/k8s_config/consul/service-splitter.yaml

• Deploy the new version of the application

git add .
git commit -m "deploying canary"
git push

• Wait for waypoint to build and deploy the new version of the application
• Look at grafana to see the health of the application
• Continuously ramp up traffic until all traffic goes to the new version
• If everything looks healthy after a couple of hours, delete the previous deployment

waypoint deployment list

waypoint deployment destroy 1

Automating the canary release deployment

To deploy a canary release, first install the configuration for Consul release controller

kubectl apply -f ./files/k8s_config/canary/payments_release.yaml

It will take about 60s or so for Consul release controller to clone your deployment renaming it payments-primary, and to set up the necessary Consul configuration.

Once this is complete you will see the Payments Primary Pods Running change from 0 to 1 in the dashboard.

You can also use cURL to see the status of the release controller

curl https://localhost:19443/v1/releases -k

[{"name":"payments","status":"state_idle","version":"2"}]

If the status is not state_idle the release controller will reject any kubernetes deployments.

To trigger a canary release you can now trigger another Waypoint build

waypoint build
waypoint deploy -release=false

Cloning the example app

export GIT_SSL_NO_VERIFY=true
git clone https://hashicraft:secret@localhost:3000/hashicraft/payments.git