This site takes a Envoy config and validates it for you. Run against actual Envoy binaries with multiple versions supported (1.16.2, 1.16.0, 1.14, 1.12)
How does it work?
It sends the config to a Lambda running Envoy in validate mode or against the config_load_check_tool and prints the results. There is a 30 second timeout on the linter due to API Gateway limitations. Extremely large configs may reach that.
Do you save any data?
No and all sessions run on ephemeral Lambda containers. But it’s best to never send any sensitive data.
Canary deployments may seem like an advanced technique that requires a team of engineers to implement.
But with the new Advanced Request Routing for ALBs (Application Load Balancer), safely releasing new versions of your application straight into production has never been easier.
First, either create a new ALB or use an existing ALB and copy its DNS name.
This repo will deploy a Lambda with a API Gateway endpoint that will redirect users to the ALB with a twist – it will add a ?id=$val GET parameter. Where $val will be an integer from 1 to 6.
# Install Serverless if you don't have it npm install serverless -g
Then run to deploy the Lambda and API Gateway
1
sls deploy
Save the endpoint of the deployed API Gateway for later.
Now, we will set up routing rules that will mimic our “application”.
Click View/edit rules
Add the rules below
It should now look like this.
Now, trying querying the API Gateway endpoint we deployed earlier.
1 out of 6 times, it should be bucketed into the canary rule.
1 2 3 4
curl -L https://dmkgpj2yxh.execute-api.us-east-1.amazonaws.com/qa/canary Id was 1 through 5 curl -L https://dmkgpj2yxh.execute-api.us-east-1.amazonaws.com/qa/canary Id is 6, you've been canaried!
That’s it! You’ve set up a canary deployment where 1/6 users are canaried.
Posted Updated Yuki Sawa Guide2 minutes read (About 304 words)
To productionalize a Spinnaker installation for high availability, one of the recommendations is to use an external Redis store, such as AWS ElasticCache. This guide will go over how to migrate a Kubernetes installation of Spinnaker to an AWS ElasticCache Redis instance using Halyard.
Node type will depend on your needs and budget, here we chose a m5.large
For Engine Version choose 3.2.10.
Configure Halyard and update Spinnaker
After the instance is created, copy the Primary Endpoint for the cluster.
If you want to update all Spinnaker services at once, place this snippet into ~/.hal/default/service-settings/redis.yml, and replace $REDIS_PRIMARY_ENDPOINT with your endpoint.