This commit is contained in:
xichengliudui 2018-10-18 23:38:01 -04:00
parent ea9d3092d9
commit 4a08aadc10
2 changed files with 3 additions and 3 deletions

View File

@ -112,7 +112,7 @@ See https://github.com/kubernetes/kubernetes/issues/53640 and https://github.com
### Non-Goals
* The new plugin mechanism will not be a "plugin installer" or wizard. It will not have specific or baked-in knowledge
regarding a plugin's location or composition, nor will it it provide a way to download or unpack plugins in a correct
regarding a plugin's location or composition, nor will it provide a way to download or unpack plugins in a correct
location.
* Plugin discovery is not a main focus of this mechanism. As such, it will not attempt to collect data about every
plugin that exists in an environment.

View File

@ -143,7 +143,7 @@ capabilities like e.g. kubeadm upgrade for HA clusters.
- This proposal doesn't provide an automated solution for transferring the CA key and other required
certs from one control-plane instance to the other. More specifically, this proposal doesn't address
the ongoing discussion about storage of kubeadm TLS assets in secrets and it it is not planned
the ongoing discussion about storage of kubeadm TLS assets in secrets and it is not planned
to provide support for clusters with TLS stored in secrets (but nothing in this
proposal should explicitly prevent to reconsider this in future).
@ -441,4 +441,4 @@ workflow we can provide better support for:
instance instead of creating a new configMap from scratch).
- Checking that the cluster/the kubeadm-config is properly configured for many control plane instances
- Blocking users trying to create secondary control plane instances on clusters with configurations
we don't want to support as a SIG (e.g. HA with self-hosted control plane)
we don't want to support as a SIG (e.g. HA with self-hosted control plane)