Automatic merge from submit-queue
Set lifecycle on ElasticIP and NAT Gateway tasks to avoid spurious changes
Identified in issue #476
Extension of fixes within PR #3226
Automatic merge from submit-queue
starting work on file assets builder
I refactored to the dockerassets pkg to assetstasks, in order to not add yet another package. Added file copy task, that I have tested with s3 locally, but not certain how to add memfs tests.
Fixes: https://github.com/kubernetes/kops/issues/3086
Automatic merge from submit-queue
Add hooks to bootstrapscript output
Ping @gambol99
Related to:
- https://github.com/kubernetes/kops/pull/3120
- https://github.com/kubernetes/kops/pull/3063
Cluster Hooks are now added in their entirety to the nodeup user data scripts, dependant on whether the instance group roles match. This could increase the size of the user-data files significantly (getting closer to the 16KB mark) depending on users' hooks content. I considered hashing and fingerprinting the cluster hooks, but following discussions in https://github.com/kubernetes/kops/pull/3120 thought we should keep the full output instead.
- removed the Mode field from the FileAsset spec
- removed the ability to template the content
- removed the need to specify the Path and instead default to /srv/kubernetes/assets/<name>
- change the FileAssets from []*FileAssets to []FileAssets
The current implementation does not make it ease to fully customize nodes before kube install. This PR adds the ability to include file assets in the cluster and instaneGroup spec which can be consumed by nodeup. Allowing those whom need (i.e. me :-)) greater flexibilty around their nodes. @Note, nothing is enforced, so unless you've specified anything everything is as the same
- updated the cluster_spec.md to reflect the changes
- permit users to place inline files into the cluster and instance group specs
- added the ability to template the files, the Cluster and InstanceGroup specs are passed into context
- cleaned up and missed comment, unordered imports etc along the journey
Automatic merge from submit-queue
Update Canal to the latest
Update Calico and Flannel versions
- Calico to v2.4.1
- Flannel to v0.8.0
The #3161 issue should be reviewed for the Default Deny NetworkPolicy behavior change this PR brings along.
Automatic merge from submit-queue
Changes on CoreOS related documentation.
- Changed "experimental" to "production-ready" status on CoreOS
images.
- Added a complete tutorial/exercise using a multi-master setup
with CoreOS
Automatic merge from submit-queue
Correctly set lifecycle on LB resources
When the cluster is configured with an ELB, the following resources show up on every update as requiring changes:
```
Will modify resources:
DNSName/api.kash-kops.example.com
Lifecycle <nil> -> Sync
LoadBalancer/api.kash-kops.example.com
Lifecycle <nil> -> Sync
LoadBalancerAttachment/api-master-eu-west-1a
Lifecycle <nil> -> Sync
LoadBalancerAttachment/api-master-eu-west-1b
Lifecycle <nil> -> Sync
LoadBalancerAttachment/api-master-eu-west-1c
Lifecycle <nil> -> Sync
```
This PR sets the lifecycle property on the above awstask objects.
Kubernetes Submit Queue
Alexander Brandstedt
andrewsykim
Kashif Saadat
Rajadeepan D Ramesh
Justin Santa Barbara
chrislovecnm
Rohith
lichuqiang
Reinaldo Martinez
Mike Splain
lsowen