OpenStack: Document breaking change when using S3 state store and gossip

This commit is contained in:
ederst 2023-10-18 16:58:19 +02:00
parent 1038071e8b
commit 8b78015917
2 changed files with 8 additions and 0 deletions

View File

@ -33,6 +33,10 @@ they would do so when the respective `topology` was set to `public`.
# Breaking changes
## OpenStack
* If storing the state in an S3 bucket, it is now required to either [deactivate gossip support](https://github.com/kubernetes/kops/issues/15684#issuecomment-1645384421) (`--dns=none`) or - for example - provide the credentials via cloud-init. Due to changes in [PR#15646](https://github.com/kubernetes/kops/pull/15646/files#diff-c1c852aea92883d3117fae99c1610c5cdcbc217f5aa3b340f23b5dd02e971d99L136-L145) the `S3_*` variables will not get passed on to the boot script of the [nodes anymore](https://github.com/kubernetes/kops/pull/15691). As a result the `kops-configuration.service` will throw an `EnvAccessKeyNotFound: failed to find credentials in the environment.` error and they will not join the cluster. Deactivating the gossip support will make the nodes contact the API servers for the bootstrap information.
## Other breaking changes
* Support for Kubernetes version 1.21 has been removed.

View File

@ -16,6 +16,10 @@
* The `kops get assets --copy` command no longer sets object-level public-read ACLs in the destination fileRepository.
## OpenStack
* If storing the state in an S3 bucket, it is now required to either [deactivate gossip support](https://github.com/kubernetes/kops/issues/15684#issuecomment-1645384421) (`--dns=none`) or - for example - provide the credentials via cloud-init. Due to changes in [PR#15646](https://github.com/kubernetes/kops/pull/15646/files#diff-c1c852aea92883d3117fae99c1610c5cdcbc217f5aa3b340f23b5dd02e971d99L136-L145) the `S3_*` variables will not get passed on to the boot script of the [nodes anymore](https://github.com/kubernetes/kops/pull/15691). As a result the `kops-configuration.service` will throw an `EnvAccessKeyNotFound: failed to find credentials in the environment.` error and they will not join the cluster. Deactivating the gossip support will make the nodes contact the API servers for the bootstrap information.
## Other breaking changes
* Support for Kubernetes version 1.22 has been removed.