Doc updates

This commit is contained in:
chrislovecnm 2017-02-07 18:42:45 -07:00
parent 9d30e532ce
commit bcbede8c90
3 changed files with 10 additions and 0 deletions

View File

@ -12,3 +12,7 @@
* Apply the rolling-update `kops rolling-update cluster ${NAME} --yes`
NOTE: rolling-update does not yet perform a real rolling update - it just shuts down machines in sequence with a delay;
there will be downtime [Issue #37](https://github.com/kubernetes/kops/issues/37)
We have implemented a new feature that does drain and validate nodes. This feature is experimental, and you can use the new feature by setting `export KOPS_FEATURE_FLAGS="+DrainAndValidateRollingUpdate"`.

View File

@ -50,6 +50,7 @@ Then restart the machines with: `kops rolling-update cluster --yes`
NOTE: rolling-update does not yet perform a real rolling update - it just shuts down machines in sequence with a delay;
there will be downtime [Issue #37](https://github.com/kubernetes/kops/issues/37)
We have implemented a new feature that does drain and validate nodes. This feature is experimental, and you can use the new feature by setting `export KOPS_FEATURE_FLAGS="+DrainAndValidateRollingUpdate"`.
## Resize an instance group

View File

@ -24,3 +24,8 @@ node restart), but currently you must:
* `kops rolling-update cluster $NAME` to preview, then `kops rolling-update cluster $NAME --yes`
Upgrade uses the latest Kubernetes version considered stable by kops, defined in `https://github.com/kubernetes/kops/blob/master/channels/stable`.
NOTE: rolling-update does not yet perform a real rolling update - it just shuts down machines in sequence with a delay;
there will be downtime [Issue #37](https://github.com/kubernetes/kops/issues/37)
We have implemented a new feature that does drain and validate nodes. This feature is experimental, and you can use the new feature by setting `export KOPS_FEATURE_FLAGS="+DrainAndValidateRollingUpdate"`.