adding IAM requirements

[fire-ant]

As the app-dev profile includes both cloudwatch and CA components we need to accompany the demo with the requisite permissions to access the AWS API's. Im not sure if Kubernetes-system is the right place (although it is the right namespace and has associated components). This could live in a separate directory for clarity but either way we need to push this config so the Autoscaler doesnt hang and the cloudwatch logs can be pushed as the demo suggests.

[stefanprodan]

@fire-ant I think this should go into the readme and not as a YAML in the repo. Flux will try to apply it on the cluster and that will fail since that YAML is an eksctl config file, not a Kubernetes resource.

[fire-ant]

oh goodness, where is my head at - Ill fire it in that direction, many thanks!

[michaelbeaumont]

We already have a reference to an example config: https://github.com/weaveworks/eks-quickstart-app-dev#pre-requisites

[michaelbeaumont]

I think the problem is that users don't see that when reading https://eksctl.io/gitops-quickstart/#standing-up-your-cluster

[stefanprodan]

With Flux2 you'll be able to add eksctl configs to the repo and exclude them from the cluster reconciliation in a declarative way using .sourceignore