liwenwu-amazon / reinvent2018-NET410

liwenwu-amazon/reinvent2018-NET410 Issues

Fix cloudformation to handle non-default vpc
Closed 6 years ago1
typo in kops demo - kubeclt should be kubectl
Updated 6 years ago1
Fix CloudFormation to handle space in ssh key-pair
Updated 6 years ago
handle kops cluster delete efficiently
Updated 6 years ago
Thinking of changing to full Title - AWS re:Invent 2018: NET410 Workshop: Deep Dive on Container Networking at Scale on Amazon EKS, Amazon ECS, & Amazon EC2
Updated 6 years ago
We need to show how eni id was obtained -aws ec2 describe-network-interfaces --network-interface-ids eni-0f96810f42e4f53e8 --region eu-west-1
Closed 6 years ago1
"Amazon EKS Architecture" diagram has text with 2017 and a floating / superimposed text
Closed 6 years ago1
We need to include cd into eks-cni-demo directory- [ec2-user@ip-172-31-23-130 reinvent2018-NET410]$ cd eks-cni-demo/
Closed 6 years ago1
show prompt before command being run - see below
Closed 6 years ago2
It might be better to have attendees get the EKS & Kops Public IP's for ssh from EC2 Console
Updated 6 years ago
# /opt/cni/bin/aws-cni-support.sh - Command missing / explanation for what is being done
Closed 6 years ago1
CNI Demo: Need to edit cluster set up portion
Closed 6 years ago1
Remove Policy Section Below to keep focus on networking
Closed 6 years ago1
eks cluster needs worker node to use t2.medium
Closed 6 years ago
kops also have options to use aws eks cni
Updated 6 years ago
Are instructions below still valid ?
Updated 6 years ago
Fix Typo in Pod Netowrk Stack Internal
Updated 6 years ago
Remove Section Below similar to to Kops section
Updated 6 years ago
[ec2-user@ip-172-31-21-42 configFiles]$ kubectl apply -f busyboxDeployment.yaml - This step was missed
Closed 6 years ago1
I think Console should be the first option to create ssh key-pair as it's the simplest
Closed 6 years ago2
[ec2-user@ip-172-31-21-42 configFiles]$ kubectl apply -f simpleHttpServer.yaml - missed step
Closed 6 years ago1
Step missed -[ec2-user@ip-172-31-21-42 configFiles]$ kubectl apply -f client.yaml
Closed 6 years ago1
Step missed -[ec2-user@ip-172-31-21-42 configFiles]$ kubectl apply -f serviceClusterIp.yaml
Closed 6 years ago3
Let's have them check the region before they start creating the ssh keys
Closed 6 years ago2
"sudo" required for commands below
Updated 6 years ago
Should we have a bold heading saying all "All Workshop activities will be done in eu-west-1" ?
Updated 6 years ago
Use IP from "kubectl get nodes -o wide" command output to make it clear this is from one of the node
Closed 6 years ago1
Please fix git clone issue
Closed 6 years ago
Fix CloudFormation template
Updated 6 years ago