Merge master into dev-1.22 to keep in sync.

content/en/docs/concepts/services-networking/dns-pod-service.md

@@ -7,6 +7,7 @@ content_type: concept
 weight: 20
 ---
 <!-- overview -->
+
 Kubernetes creates DNS records for services and pods. You can contact
 services with consistent DNS names instead of IP addresses. 
 
@@ -261,6 +262,8 @@ spec:
 
 ### Pod's DNS Config {#pod-dns-config}
 
+{{< feature-state for_k8s_version="v1.14" state="stable" >}}
+
 Pod's DNS Config allows users more control on the DNS settings for a Pod.
 
 The `dnsConfig` field is optional and it can work with any `dnsPolicy` settings.
@@ -332,7 +335,6 @@ The availability of Pod DNS Config and DNS Policy "`None`" is shown as below.
 | 1.9 | Alpha |
 
 
-
 ## {{% heading "whatsnext" %}}
 
 

content/en/docs/concepts/services-networking/endpoint-slices.md

@@ -249,5 +249,4 @@ implementation in `kube-proxy`.
 
 ## {{% heading "whatsnext" %}}
 
-* Learn about [Enabling EndpointSlices](/docs/tasks/administer-cluster/enabling-endpointslices)
 * Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)

content/en/docs/concepts/services-networking/service.md

@@ -215,7 +215,7 @@ each Service port. The value of this field is mirrored by the corresponding
 Endpoints and EndpointSlice objects.
 
 This field follows standard Kubernetes label syntax. Values should either be
-[IANA standard service names](http://www.iana.org/assignments/service-names) or
+[IANA standard service names](https://www.iana.org/assignments/service-names) or
 domain prefixed names such as `mycompany.com/my-custom-protocol`.
 
 ## Virtual IPs and service proxies