Revert v1.17 release changes on v1.16 branch (#18123)

This reverts commits:
  1131f8603e.
  cf5b8b200c.
  75de70a431.
  dff2f7b960.
  cf925bb688.
  ffd1363c0e.
  87a2cafb20.
  ffe259d6f2.

content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md

@@ -154,8 +154,6 @@ spec:
 
 ## Garbage Collecting Load Balancers
 
-{{< feature-state for_k8s_version="v1.17" state="stable" >}}
-
 In usual case, the correlating load balancer resources in cloud provider should
 be cleaned up soon after a LoadBalancer type Service is deleted. But it is known
 that there are various corner cases where cloud resources are orphaned after the
@@ -169,6 +167,10 @@ The finalizer will only be removed after the load balancer resource is cleaned u
 This prevents dangling load balancer resources even in corner cases such as the
 service controller crashing.
 
+This feature is beta and enabled by default since Kubernetes v1.16. You can also
+enable it in v1.15 (alpha) via the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
+`ServiceLoadBalancerFinalizer`.
+
 ## External Load Balancer Providers
 
 It is important to note that the datapath for this functionality is provided by a load balancer external to the Kubernetes cluster.