weaveworks / eks-appmesh-profile Goto Github PK

Could we change back some of the elements of the welcome page?
I made edits in this google doc: https://docs.google.com/document/d/1qvS0mssHjzICPSHH3TCyu6AUbxPFrRDzRHpPn156FcQ/edit#heading=h.6uidh43o18i4

LMK. Thanks!

Create App Mesh inject HelmRelease

Add Jaeger HelmRelease to the profile and configure tracing in App Mesh Inject.

Create metrics server HelmRelease (required by Flagger canary HPA)

It's unclear what permissions are needed to complete the hands-on demo :(
After spending an inordinate amount of time in the AWS IAM console... I surrendered...

I added full administrative access to the IAM role and yet, still nothing! What's missing?

[ℹ]  eksctl version 0.10.1
[ℹ]  using region us-west-2
[✖]  getting availability zones: getting availability zones for us-west-2: OptInRequired: You are not subscribed to this service. Please go to http://aws.amazon.com to subscribe.
	status code: 401, request id: a3824087-ca85-4acc-a326-6413e2c2fa54

Depends on aws/eks-charts#41

[ ] App Mesh CRDs
[ ] App Mesh controller HelmRelease

Create a demo profile with:

• demo app (podinfo)
• expose the app outside the mesh (Envoy ingress + ELB)
• load testing service for canary releases (Flagger tester)

Create a HelmRelease for Flagger configured with App Mesh.

Create a hands-on workshop to showcase:

• App Mesh installation on EKS
• GitOps workflow for a demo app running on App Mesh
• Progressive delivery with Flagger and Prometheus
• Conformance testing for canary releases

Update CRDs and helm releases.

Add the App Mesh Gateway helm release to profile.

Create App Mesh Prometheus HelmRelease

Currently the demo for Progressive Delivery from:

https://eks.handson.flagger.dev/profile/#install-app-mesh

and

https://weaveworks-gitops.awsworkshop.io/50_workshop_5_accelerating_sdlc/30_install_appmesh/01_install_app_mesh.html

point to the demo branch of this repo.

the demo/ingress/appmesh-gateway.yaml however needs to be modified to stop using a deprecated Chart that is no longer supported and use the official eks-chart.

The chart change however creates some additional work because the old chart required mesh.name parameter and the new one does not have anything equivalent.

Add A/B testing based on HTTP headers match conditions to the demo.