cloud-images

~rcj/cloud-images/+git/aws-eks-website:build/20180513.1

  1. Git
  2. lp:~rcj/cloud-images/+git/aws-eks-website
  3. build/20180513.1
Last commit made on 2018-06-14
Get this branch:
git clone -b build/20180513.1 https://git.launchpad.net/~rcj/cloud-images/+git/aws-eks-website
Only Robert C Jennings can upload to this branch. If you are Robert C Jennings please log in for upload directions.

Branch merges

Branch information

Name:
build/20180513.1
Repository:
lp:~rcj/cloud-images/+git/aws-eks-website

Recent commits

9a9b353... by Robert C Jennings

Change AMI link to provide an image list via the web console

9cf630d... by Robert C Jennings

Update for 20180613.1 Serial

* Remove hardcoded region in cluster name resolution (LP: #1776498)

* Set max-pods option for kubelet

* Remove Pre-GA code to add EKS subcmd to aws-cli
  Cleanup Post-GA now that the aws-cli has been updated to include
  the 'eks' sub-command

* Signal success/failure to cloudformation
  Copied this concept from the AWS user-data but used aws-cli rather
  that unpackaged CF utils. This lays the groundwork for users
  to edit the CF template to watch for success/failure to know if
  node roll-back is necessary. The option is not added to the
  template because any failure deletes the VM; which is hard to debug
  for new users. Rather the end-user should enable it if they decide
  it is best for their environment, and after qualification testing.

 TODO: Add doc to webpage pointing out the 'WaitOnResourceSignals'
 property in the AutoScaling Update Policy docs @
 https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-updatepolicy.html#cfn-attributes-updatepolicy-rollingupdate-waitonresourcesignals

a80cfc2... by Robert C Jennings

Initial commit. EKS 1.10.3 (20180605 serial AMI)