Header-based routing doesn't work

[aldredb]

There are issues running the commands in: https://www.appmeshworkshop.com/policyrouting/curljson/

curl --location --header "canary_fleet: true" --silent $URL/json gives 404 error as there is no /json path

Even though header is set to canary_fleet: true, Crystal service still randomly gives non-canary response back. This is probably because Ruby front-end does not forward the header to Crystal service. The only reliable way to get 100% canary response is to open a Session Manager session against the External EC2 instance and access the Virtual Gateway of the Crystal service (created in in https://www.appmeshworkshop.com/virtualgateway/crystal-ingress/) i.e.

for ((i=1;i<=15;i++)); do
 curl --header "canary_fleet: true" $NLB_ENDPOINT/ecs/crystal
 sleep 1s
done