aws-workshop-for-kubernetes
aws-workshop-for-kubernetes copied to clipboard
aws-samples
AWS Workshop for Kubernetes
*Issue #, if available (include [keywords](https://help.github.com/articles/closing-issues-using-keywords/) to close issue as applicable, e.g. "fixes "):* *Description of changes:* By submitting this pull request, I confirm that my contribution is made under...
* zsh 5.3.1 * kubectl version : v1.9.1 A command [here](https://github.com/aws-samples/aws-workshop-for-kubernetes/tree/master/developer-concepts#default-memory-and-cpu) doesn't return the result as expected. Instead of it, a command below works. (containers[] -> containers..) `kubectl get pod/nginx-pod...
apiserver targets return a 403, presumably because EKS doesn't expose a `/metrics` endpoint. Should be called out if this workshop is being adapted for EKS.
*Description of changes:* - This changes the navigation link, which is broken in section 201 to 307 By submitting this pull request, I confirm that my contribution is made under...
*Description of changes:* - This changes the example of port forwarding that is currently generating an error by using the example By submitting this pull request, I confirm that my...
fixes #571 #559 #411 *Description of changes:* Changed navigations with broken links and also a page index. By submitting this pull request, I confirm that my contribution is made under...
Source page: https://github.com/aws-samples/aws-workshop-for-kubernetes/tree/master/02-path-working-with-clusters/201-cluster-monitoring Text with broken link: Deploying applications using Kubernetes Helm charts. Link referred: https://github.com/aws-samples/aws-workshop-for-kubernetes/blob/master/03-path-application-development/306-app-management-with-helm Fix suggestion: 306 to be replaced with 307
Current deployment method breaks when joining worker nodes. Should use eksctl to match current EKS docs.
1.10 is not supported. We should be using the most recent EKS version (1.14.7).
*Issue #, if available (include [keywords](https://help.github.com/articles/closing-issues-using-keywords/) to close issue as applicable, e.g. "fixes "):* *Description of changes:* A few spelling fixes By submitting this pull request, I confirm that my...
