Open mpatters72 opened 6 years ago
Hi @mpatters72
Thanks for feedback on the workshop. I am a little hesitant to propose using single account in a group setting. If we get into that territory, we get into customized delivery of workshop content which is totally up to the speakers/audience if they want to consume it that way. We want to keep this workshop consumption as simple as it can and focus on enabling individual tutorials which is the meat of this workshop. For ex, if customers want to learn how to use Prometheus, Istio/Envoy, Helm charts on top of k8s cluster on AWS, they should find most current information.
I like your suggestion on better separation between kops and non-kops (EKS), and other suggestions like updating env variables. Please send us a PR so we can review it
@dalbhanj can you assign this to me? i'm working directly w/ @mpatters72 on these edits.
/assign @cloudymind
During upcoming training session we have 10+ people using the same AWS account. A few simple changes could avoid name collisions.
Cloudformation templates:
k8s-workshop
tok8s-workshop-myname
k8s-workshop
, use this as cloudformation output. Either Instruct people to change name in the cloudformation e.gk8s-workshop-mike
or let them use defaultlab-ide-build.sh
./create-kubeconfig.sh
$EKS_CLUSTER_NAME
, pass cluster name as variable, or use override if provided our fall back to hard-coded default.Various other places
Other feedback
create-the-master-nodes
Cc @cloudymind