Update feature flags and rolling update description

AdamDang · Dec 28, 2017 · d9d645c · d9d645c
1 parent 7608bca
commit d9d645c
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 4 deletions.
diff --git a/docs/experimental.md b/docs/experimental.md
@@ -7,5 +7,9 @@ Enable experimental features with:
 The following experimental features are currently available:
 
 * `+VSphereCloudProvider` - Enable vSphere cloud provider.
-* `+DrainAndValidateRollingUpdate` - Enable drain and validate for rolling updates.
 * `+EnableExternalDNS` - Enable external-dns with default settings (ingress sources only).
+* `+VPCSkipEnableDNSSupport` - Enables creation of a VPC that does not need DNSSupport enabled.
+* `+SkipTerraformFormat` - Do not `terraform fmt` the generated terraform files.
+* `+EnableExternalCloudController` - Enables the use of cloud-controller-manager introduced in v1.7.
+* `+EnableSeparateConfigBase` - Allow a config-base that is different from the state store.
+* `+SpecOverrideFlag` - Allow setting spec values on `kops create`.
diff --git a/docs/instance_groups.md b/docs/instance_groups.md
@@ -48,9 +48,7 @@ See a preview with: `kops rolling-update cluster`
 
 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"`.
+This will drain nodes, restart them with the new instance type, and validate them after startup.
 
 ## Resize an instance group