Merge branch 'master' into patch-1

Author: viniciusbds

OWNERS

@@ -7,10 +7,10 @@ approvers:
 - sig-docs-en-owners # Defined in OWNERS_ALIASES
 
 emeritus_approvers:
-- chenopis
-- jaredbhatti
+# chenopis, you're welcome to return when you're ready to resume PR wrangling
+# jaredbhatti, you're welcome to return when you're ready to resume PR wrangling
 # stewart-yu, you're welcome to return when you're ready to resume PR wrangling
 - stewart-yu 
 
 labels:
-- sig/docs
+- sig/docs

OWNERS_ALIASES

@@ -48,6 +48,7 @@ aliases:
     - makoscafee
     - onlydole
     - Rajakavitha1
+    - savitharaghunathan
     - sftim
     - steveperry-53
     - tengqm

README-uk.md

@@ -19,6 +19,19 @@
 * [Керівництво зі стилю оформлення документації](http://kubernetes.io/docs/contribute/style/style-guide/)
 * [Переклад документації Kubernetes іншими мовами](https://kubernetes.io/docs/contribute/localization/)
 
+## Файл `README.md` іншими мовами
+
+|                               |                               |
+|-------------------------------|-------------------------------|
+| [Англійська](README.md)       | [Французька](README-fr.md)    |
+| [Корейська](README-ko.md)     | [Німецька](README-de.md)      |
+| [Португальська](README-pt.md) | [Хінді](README-hi.md)         |
+| [Іспанська](README-es.md)     | [Індонезійська](README-id.md) |
+| [Китайська](README-zh.md)     | [Японська](README-ja.md)      |
+| [В'єтнамська](README-vi.md)   | [Російська](README-ru.md)     |
+| [Італійська](README-it.md)    | [Польська](README-pl.md)      |
+|                               |                               |
+
 ## Запуск сайту локально за допомогою Docker
 
 Для локального запуску сайту Kubernetes рекомендовано запустити спеціальний [Docker](https://docker.com)-образ, що містить генератор статичних сайтів [Hugo](https://gohugo.io).

assets/sass/_desktop.sass

@@ -2,7 +2,7 @@ $main-max-width: 1200px
 $vendor-strip-height: 44px
 $video-section-height: 550px
 
-@media screen and (min-width: 1025px)
+@media screen and (min-width: 1100px)
   #hamburger
     display: none
 

content/de/includes/user-guide-migration-notice.md

@@ -24,17 +24,17 @@ The new concept of a path type allows you to specify how a path should be matche
 The Ingress resource was designed with simplicity in mind, providing a simple set of fields that would be applicable in all use cases. Over time, as use cases evolved, implementations began to rely on a long list of custom annotations for further configuration. The new `IngressClass` resource provides a way to replace some of those annotations.
 
 Each `IngressClass` specifies which controller should implement Ingresses of the class and can reference a custom resource with additional parameters. 
-```
-apiVersion: networking.k8s.io/v1beta1
-kind: IngressClass
+```yaml
+apiVersion: "networking.k8s.io/v1beta1"
+kind: "IngressClass"
 metadata:
-  name: external-lb
+  name: "external-lb"
 spec:
-  controller: example.com/ingress-controller
+  controller: "example.com/ingress-controller"
   parameters:
-    apiGroup: k8s.example.com/v1alpha
-    kind: IngressParameters
-    name: external-lb
+    apiGroup: "k8s.example.com/v1alpha"
+    kind: "IngressParameters"
+    name: "external-lb"
 ```
 
 ### Specifying the Class of an Ingress
@@ -60,21 +60,21 @@ Many Ingress providers have supported wildcard hostname matching like `*.foo.com
 ### Putting it All Together
 These new Ingress features allow for much more configurability. Here’s an example of an Ingress that makes use of pathType, `ingressClassName`, and a hostname wildcard:
 
-```
-apiVersion: networking.k8s.io/v1beta1
-kind: Ingress
+```yaml
+apiVersion: "networking.k8s.io/v1beta1"
+kind: "Ingress"
 metadata:
-  name: example-ingress
+  name: "example-ingress"
 spec:
-  ingressClassName: external-lb
+  ingressClassName: "external-lb"
   rules:
-  - host: *.example.com
+  - host: "*.example.com"
     http:
       paths:
-      - path: /example
-        pathType: Prefix
+      - path: "/example"
+        pathType: "Prefix"
         backend:
-          serviceName: example-service
+          serviceName: "example-service"
           servicePort: 80
 ```
 

content/en/blog/_posts/2020-04-02-Improvements-to-the-Ingress-API-in-Kubernetes-1.18.md

@@ -231,6 +231,7 @@ The following cloud providers have implemented CCMs:
 * [DigitalOcean](https://github.com/digitalocean/digitalocean-cloud-controller-manager)
 * [GCP](https://github.com/kubernetes/cloud-provider-gcp)
 * [Hetzner](https://github.com/hetznercloud/hcloud-cloud-controller-manager)
+* [HUAWEI CLOUD](https://github.com/kubernetes-sigs/cloud-provider-huaweicloud)
 * [Linode](https://github.com/linode/linode-cloud-controller-manager)
 * [OpenStack](https://github.com/kubernetes/cloud-provider-openstack)
 * [Oracle](https://github.com/oracle/oci-cloud-controller-manager)

content/en/docs/concepts/architecture/cloud-controller.md

@@ -52,7 +52,7 @@ Job is a Kubernetes resource that runs a
 {{< glossary_tooltip term_id="pod" >}}, or perhaps several Pods, to carry out
 a task and then stop.
 
-(Once [scheduled](/docs/concepts/scheduling/), Pod objects become part of the
+(Once [scheduled](/docs/concepts/scheduling-eviction/), Pod objects become part of the
 desired state for a kubelet).
 
 When the Job controller sees a new task it makes sure that, somewhere

content/en/docs/concepts/architecture/controller.md

@@ -140,7 +140,7 @@ deployment.apps/my-deployment created
 persistentvolumeclaim/my-pvc created
 ```
 
-The `--recursive` flag works with any operation that accepts the `--filename,-f` flag such as: `kubectl {create,get,delete,describe,rollout} etc.`
+The `--recursive` flag works with any operation that accepts the `--filename,-f` flag such as: `kubectl {create,get,delete,describe,rollout}` etc.
 
 The `--recursive` flag also works when multiple `-f` arguments are provided:
 
@@ -453,7 +453,7 @@ That's it! The Deployment will declaratively update the deployed nginx applicati
 
 {{% capture whatsnext %}}
 
-- [Learn about how to use `kubectl` for application introspection and debugging.](/docs/tasks/debug-application-cluster/debug-application-introspection/)
-- [Configuration Best Practices and Tips](/docs/concepts/configuration/overview/)
+- Learn about [how to use `kubectl` for application introspection and debugging](/docs/tasks/debug-application-cluster/debug-application-introspection/).
+- See [Configuration Best Practices and Tips](/docs/concepts/configuration/overview/).
 
 {{% /capture %}}