Update logic for cloudconfig in S3 bucket

Question

rossf7 opened this issue 7 years ago · comments

Towards giantswarm/giantswarm#2023

Currently we update the cloud config in the S3 bucket when clusters are reprocessed. This can cause problems if breaking changes are deployed.

In k8scloudconfig we want to use semver to identify breaking / non breaking changes.
We also need to version the cloudconfig stored in the S3 bucket.
For non breaking changes we should update the existing cloud config and roll the nodes to apply the changes.
For breaking changes a new version should be created in the S3 bucket and the cluster should not be updated.

Cloud Config operator

Until the cloud config operator is in place aws-operator will need to determine which k8scloudconfig version to use.
Once the cloud config operator is in place it will generate the cloud config but aws-operator will still need to upload it to S3.

xh3b4sd · Answer 1 · Wed Dec 06 2017 18:09:54 GMT+0800 (China Standard Time)

@rossf7 please have a look again and sort the issue from an organizational point of view. <3

Ross Fairbanks · Answer 2 · Tue Dec 12 2017 19:40:28 GMT+0800 (China Standard Time)

Moving this to Team Batman as its part of the AWS updates story.

Ross Fairbanks · Answer 3 · Mon Aug 27 2018 21:41:35 GMT+0800 (China Standard Time)

Closing. This is ancient and superseded by work done on the updates story.