Skip to content

Commit 17aaf34

Browse files
k8s-ci-robotk8s-ci-robot
authored
Merge pull request #46234 from dipesh-rawat/blog-post-2019-add-author
Update 2019 blog content files to move author details in front-matter
2 parents 936c036 + eacbfdc commit 17aaf34

File tree

52 files changed

+142
-114
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

52 files changed

+142
-114
lines changed

‎content/en/blog/_posts/2019-01-14-apiserver-dry-run-and-kubectl-diff.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
layout: blog
33
title: 'APIServer dry-run and kubectl diff'
44
date: 2019-01-14
5+
author: >
6+
Antoine Pelisse (Google Cloud)
57
---
68

7-
**Author**: Antoine Pelisse (Google Cloud, @apelisse)
8-
99
Declarative configuration management, also known as configuration-as-code, is
1010
one of the key strengths of Kubernetes. It allows users to commit the desired state of
1111
the cluster, and to keep track of the different versions, improve auditing and

‎content/en/blog/_posts/2019-01-15-container-storage-interface-ga.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22
title: Container Storage Interface (CSI) for Kubernetes GA
33
date: 2019-01-15
44
slug: container-storage-interface-ga
5+
author: >
6+
Saad Ali (Google)
57
---
68

79
![Kubernetes Logo](/images/blog-logging/2018-04-10-container-storage-interface-beta/csi-kubernetes.png)
810
![CSI Logo](/images/blog-logging/2018-04-10-container-storage-interface-beta/csi-logo.png)
911

10-
**Author:** Saad Ali, Senior Software Engineer, Google
11-
1212
The Kubernetes implementation of the [Container Storage Interface](https://github.com/container-storage-interface/spec/blob/master/spec.md) (CSI) has been promoted to GA in the Kubernetes v1.13 release. Support for CSI was [introduced as alpha](http://blog.kubernetes.io/2018/01/introducing-container-storage-interface.html) in Kubernetes v1.9 release, and [promoted to beta](https://kubernetes.io/blog/2018/04/10/container-storage-interface-beta/) in the Kubernetes v1.10 release.
1313

1414
The GA milestone indicates that Kubernetes users may depend on the feature and its API without fear of backwards incompatible changes in future causing regressions. GA features are protected by the [Kubernetes deprecation policy](/docs/reference/using-api/deprecation-policy/).

‎content/en/blog/_posts/2019-01-17-update-volume-snapshot-alpha.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
22
title: Update on Volume Snapshot Alpha for Kubernetes
33
date: 2019-01-17
4+
author: >
5+
DJing Xu (Google),
6+
Xing Yang (Huawei),
7+
Saad Ali (Google)
48
---
59

6-
**Authors:** Jing Xu (Google), Xing Yang (Huawei), Saad Ali (Google)
7-
810
Volume snapshotting support was introduced in Kubernetes v1.12 as an alpha feature. In Kubernetes v1.13, it remains an alpha feature, but a few enhancements were added and some breaking changes were made. This post summarizes the changes.
911

1012
## Breaking Changes

‎content/en/blog/_posts/2019-02-06-poseidon-firmament-scheduler-announcement.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
---
22
title: Poseidon-Firmament Scheduler – Flow Network Graph Based Scheduler
33
date: 2019-02-06
4+
author: >
5+
Deepak Vij (Huawei),
6+
Shivram Shrivastava (Huawei)
47
---
58

6-
**Authors:** Deepak Vij (Huawei), Shivram Shrivastava (Huawei)
7-
89
## Introduction
910

1011
Cluster Management systems such as Mesos, Google Borg, Kubernetes etc. in a cloud scale datacenter environment (also termed as ***Datacenter-as-a-Computer*** or ***Warehouse-Scale Computing - WSC***) typically manage application workloads by performing tasks such as tracking machine live-ness, starting, monitoring, terminating workloads and more importantly using a **Cluster Scheduler** to decide on workload placements.

‎content/en/blog/_posts/2019-02-11-runc-CVE-2019-5736.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
title: Runc and CVE-2019-5736
33
date: 2019-02-11
44
evergreen: false # mentions PodSecurityPolicy
5+
author: >
6+
Kubernetes Product Security Committee
57
---
68

7-
Authors: Kubernetes Product Security Committee
8-
99
This morning [a container escape vulnerability in runc was announced](https://www.openwall.com/lists/oss-security/2019/02/11/2). We wanted to provide some guidance to Kubernetes users to ensure everyone is safe and secure.
1010

1111
## What is runc?

‎content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,13 @@
22
title: Building a Kubernetes Edge (Ingress) Control Plane for Envoy v2
33
date: 2019-02-12
44
slug: building-a-kubernetes-edge-control-plane-for-envoy-v2
5+
author: >
6+
Daniel Bryant (Datawire),
7+
Flynn (Datawire),
8+
Richard Li (Datawire)
59
---
610

711

8-
**Author:**
9-
Daniel Bryant, Product Architect, Datawire;
10-
Flynn, Ambassador Lead Developer, Datawire;
11-
Richard Li, CEO and Co-founder, Datawire
12-
13-
1412
Kubernetes has become the de facto runtime for container-based microservice applications, but this orchestration framework alone does not provide all of the infrastructure necessary for running a distributed system. Microservices typically communicate through Layer 7 protocols such as HTTP, gRPC, or WebSockets, and therefore having the ability to make routing decisions, manipulate protocol metadata, and observe at this layer is vital. However, traditional load balancers and edge proxies have predominantly focused on L3/4 traffic. This is where the [Envoy Proxy](https://www.envoyproxy.io/) comes into play.
1513

1614
Envoy proxy was designed as a [universal data plane](https://blog.envoyproxy.io/the-universal-data-plane-api-d15cec7a) from the ground-up by the Lyft Engineering team for today's distributed, L7-centric world, with broad support for L7 protocols, a real-time API for managing its configuration, first-class observability, and high performance within a small memory footprint. However, Envoy's vast feature set and flexibility of operation also makes its configuration highly complicated -- this is evident from looking at its rich but verbose [control plane](https://blog.envoyproxy.io/service-mesh-data-plane-vs-control-plane-2774e720f7fc) syntax.

‎content/en/blog/_posts/2019-02-28-automate-operations-on-your-cluster-with-operatorhub.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
---
22
title: Automate Operations on your Cluster with OperatorHub.io
33
date: 2019-02-28
4+
author: >
5+
Diane Mueller (Red Hat)
46
---
57

6-
**Author:**
7-
Diane Mueller, Director of Community Development, Cloud Platforms, Red Hat
8-
98
One of the important challenges facing developers and Kubernetes administrators has been a lack of ability to quickly find common services that are operationally ready for Kubernetes. Typically, the presence of an Operator for a specific service - a pattern that was introduced in 2016 and has gained momentum - is a good signal for the operational readiness of the service on Kubernetes. However, there has to date not existed a registry of Operators to simplify the discovery of such services.
109

1110
To help address this challenge, today Red Hat is launching OperatorHub.io in collaboration with AWS, Google Cloud and Microsoft. OperatorHub.io enables developers and Kubernetes administrators to find and install curated Operator-backed services with a base level of documentation, active maintainership by communities or vendors, basic testing, and packaging for optimized life-cycle management on Kubernetes.

‎content/en/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Raw Block Volume support to Beta
33
date: 2019-03-07
4+
author: >
5+
Ben Swartzlander (NetApp),
6+
Saad Ali (Google)
47
---
58

6-
**Authors:**
7-
Ben Swartzlander (NetApp), Saad Ali (Google)
8-
99
Kubernetes v1.13 moves raw block volume support to beta. This feature allows persistent volumes to be exposed inside containers as a block device instead of as a mounted file system.
1010

1111
## What are block devices?

‎content/en/blog/_posts/2019-03-15-Kubernetes-setup-using-Ansible-and-Vagrant.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
layout: blog
33
title: Kubernetes Setup Using Ansible and Vagrant
44
date: 2019-03-15
5+
author: >
6+
Naresh L J (Infosys)
57
---
68

7-
**Author:** Naresh L J (Infosys)
8-
99
## Objective
1010
This blog post describes the steps required to setup a multi node Kubernetes cluster for development purposes. This setup provides a production-like cluster that can be setup on your local machine.
1111

‎content/en/blog/_posts/2019-03-19-kubeedge-k8s-based-edge-intro.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,11 @@
22
title: KubeEdge, a Kubernetes Native Edge Computing Framework
33
date: 2019-03-19
44
slug: kubeedge-k8s-based-edge-intro
5+
author: >
6+
Sanil Kumar D (Huawei),
7+
Jun Du(Huawei)
58
---
69

7-
**Author:** Sanil Kumar D (Huawei), Jun Du(Huawei)
8-
910
## KubeEdge becomes the first Kubernetes Native Edge Computing Platform with both Edge and Cloud components open sourced!
1011

1112
Open source edge computing is going through its most dynamic phase of development in the industry. So many open source platforms, so many consolidations and so many initiatives for standardization! This shows the strong drive to build better platforms to bring cloud computing to the edges to meet ever increasing demand. [KubeEdge](https://github.com/kubeedge/kubeedge), which was announced last year, now brings great news for cloud native computing! It provides a complete edge computing solution based on Kubernetes with separate cloud and edge core modules. Currently, both the cloud and edge modules are open sourced.

‎content/en/blog/_posts/2019-03-20-A-Look-Back-And-Whats-In-Store-For-Kubernetes-Contributor-Summits.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ title: A Look Back and What's in Store for Kubernetes Contributor Summits
33
date: 2019-03-20
44
layout: blog
55
evergreen: true
6+
author: >
7+
Paris Pittman (Google),
8+
Jonas Rosland (VMware)
69
---
710

8-
**Authors:**
9-
Paris Pittman (Google), Jonas Rosland (VMware)
10-
1111
{{<figure width="600" src="/images/blog/2019-03-14-A-Look-Back-And-Whats-In-Store-For-Kubernetes-Contributor-Summits/celebrationsig.jpg" caption="Seattle Contributor Summit">}}
1212

1313
As our contributing community grows in great numbers, with more than 16,000 contributors this year across 150+ GitHub repositories, it’s important to provide face to face connections for our large distributed teams to have opportunities for collaboration and learning. In [Contributor Experience], our methodology with planning events is a lot like our documentation; we build from personas -- interests, skills, and motivators to name a few. This way we ensure there is valuable content and learning for everyone.

‎content/en/blog/_posts/2019-03-21-a-guide-to-kubernetes-admission-controllers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: A Guide to Kubernetes Admission Controllers
33
date: 2019-03-21
4+
author: >
5+
Malte Isberner (StackRox)
46
---
57

6-
**Author:** Malte Isberner (StackRox)
7-
88
Kubernetes has greatly improved the speed and manageability of backend clusters in production today. Kubernetes has emerged as the de facto standard in container orchestrators thanks to its flexibility, scalability, and ease of use. Kubernetes also provides a range of features that secure production workloads. A more recent introduction in security features is a set of plugins called “[admission controllers](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/).” Admission controllers must be enabled to use some of the more advanced security features of Kubernetes, such as [pod security policies](https://kubernetes.io/docs/concepts/policy/pod-security-policy/) that enforce a security configuration baseline across an entire namespace. The following must-know tips and tricks will help you leverage admission controllers to make the most of these security capabilities in Kubernetes.
99

1010
## What are Kubernetes admission controllers?

‎content/en/blog/_posts/2019-03-22-e2e-testing-for-everyone.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Kubernetes End-to-end Testing for Everyone
33
date: 2019-03-22
4+
author: >
5+
Patrick Ohly (Intel)
46
---
57

6-
**Author:** Patrick Ohly (Intel)
7-
88
More and more components that used to be part of Kubernetes are now
99
being developed outside of Kubernetes. For example, storage drivers
1010
used to be compiled into Kubernetes binaries, then were moved into

‎content/en/blog/_posts/2019-03-25-1-14-release-announcement.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@ title: 'Kubernetes 1.14: Production-level support for Windows Nodes, Kubectl Upd
33
date: 2019-03-25
44
slug: kubernetes-1-14-release-announcement
55
evergreen: true
6+
author: >
7+
[Kubernetes v1.14 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.14/release_team.md)
68
---
79

8-
**Authors:** The 1.14 [Release Team](https://bit.ly/k8s114-team)
9-
1010
We’re pleased to announce the delivery of Kubernetes 1.14, our first release of 2019!
1111

1212
Kubernetes 1.14 consists of 31 enhancements: 10 moving to stable, 12 in beta, and 7 net new. The main themes of this release are extensibility and supporting more workloads on Kubernetes with three major features moving to general availability, and an important security feature moving to beta.

‎content/en/blog/_posts/2019-03-28-PID-Limiting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: 'Process ID Limiting for Stability Improvements in Kubernetes 1.14'
33
date: 2019-04-15
4+
author: >
5+
Derek Carr
46
---
57

6-
**Author: Derek Carr**
7-
88
Have you ever seen someone take more than their fair share of the cookies? The one person who reaches in and grabs a half dozen fresh baked chocolate chip chunk morsels and skitters off like Cookie Monster exclaiming “Om nom nom nom.”
99

1010
In some rare workloads, a similar occurrence was taking place inside Kubernetes clusters. With each Pod and Node, there comes a finite number of possible process IDs (PIDs) for all applications to share. While it is rare for any one process or pod to reach in and grab all the PIDs, some users were experiencing resource starvation due to this type of behavior. So in Kubernetes 1.14, we introduced an enhancement to mitigate the risk of a single pod monopolizing all of the PIDs available.

‎content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
---
22
title: 'Running Kubernetes locally on Linux with Minikube - now with Kubernetes 1.14 support'
3-
date: 2019-03-28
3+
date: 2019-03-28
4+
author: >
5+
[Ihor Dvoretskyi](https://twitter.com/idvoretskyi) (Cloud Native Computing Foundation)
46
---
5-
**Author**: [Ihor Dvoretskyi](https://twitter.com/idvoretskyi), Developer Advocate, Cloud Native Computing Foundation
67

78
<center>{{<figure width="600" src="/images/blog/2019-03-28-running-kubernetes-locally-on-linux-with-minikube/ihor-dvoretskyi-1470985-unsplash.jpg">}}</center>
89

‎content/en/blog/_posts/2019-03-29-kube-proxy-subtleties-debugging-an-intermittent-connection-resets.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: 'kube-proxy Subtleties: Debugging an Intermittent Connection Reset'
33
date: 2019-03-29
4+
author: >
5+
[Yongkun Gui](mailto:[email protected]) (Google)
46
---
57

6-
**Author:** [Yongkun Gui](mailto:[email protected]), Google
7-
88
I recently came across a bug that causes intermittent connection resets. After
99
some digging, I found it was caused by a subtle combination of several different
1010
network subsystems. It helped me understand Kubernetes networking better, and I

‎content/en/blog/_posts/2019-04-01-kubernetes-v1-14-delivers-production-level-support-for-nodes-and-windows-containers.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,11 @@
11
---
22
title: 'Kubernetes v1.14 delivers production-level support for Windows nodes and Windows containers'
33
date: 2019-04-01
4+
author: >
5+
Michael Michael (VMware),
6+
Patrick Lang (Microsoft)
47
---
58

6-
**Authors:** Michael Michael (VMware), Patrick Lang (Microsoft)
7-
89
The first release of Kubernetes in 2019 brings a highly anticipated feature - production-level support for Windows workloads. Up until now Windows node support in Kubernetes has been in beta, allowing many users to experiment and see the value of Kubernetes for Windows containers. While in beta, developers in the Kubernetes community and Windows Server team worked together to improve the container runtime, build a continuous testing process, and complete features needed for a good user experience. Kubernetes now officially supports adding Windows nodes as worker nodes and scheduling Windows containers, enabling a vast ecosystem of Windows applications to leverage the power of our platform.
910

1011
As Windows developers and devops engineers have been adopting containers over the last few years, they've been looking for a way to manage all their workloads with a common interface. Kubernetes has taken the lead for container orchestration, and this gives users a consistent way to manage their container workloads whether they need to run on Linux or Windows.

‎content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,12 @@
22
layout: blog
33
title: 'Kubernetes 1.14: Local Persistent Volumes GA'
44
date: 2019-04-04
5+
author: >
6+
Michelle Au (Google),
7+
Matt Schallert (Uber),
8+
Celina Ward (Uber)
59
---
610

7-
**Authors**: Michelle Au (Google), Matt Schallert (Uber), Celina Ward (Uber)
8-
911
The [Local Persistent Volumes](https://kubernetes.io/docs/concepts/storage/volumes/#local)
1012
feature has been promoted to GA in Kubernetes 1.14.
1113
It was first introduced as alpha in Kubernetes 1.7, and then

‎content/en/blog/_posts/2019-04-16-pod-priority-and-preemption-in-kubernetes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
layout: blog
33
title: 'Pod Priority and Preemption in Kubernetes'
44
date: 2019-04-16
5+
author: >
6+
Bobby Salamat
57
---
68

7-
**Author**: Bobby Salamat
8-
99
Kubernetes is well-known for running scalable workloads. It scales your workloads based on their resource usage. When a workload is scaled up, more instances of the application get created. When the application is critical for your product, you want to make sure that these new instances are scheduled even when your cluster is under resource pressure. One obvious solution to this problem is to over-provision your cluster resources to have some amount of slack resources available for scale-up situations. This approach often works, but costs more as you would have to pay for the resources that are idle most of the time.
1010

1111
[Pod priority and preemption](/docs/concepts/scheduling-eviction/pod-priority-preemption/) is a scheduler feature made generally available in Kubernetes 1.14 that allows you to achieve high levels of scheduling confidence for your critical workloads without overprovisioning your clusters. It also provides a way to improve resource utilization in your clusters without sacrificing the reliability of your essential workloads.

‎content/en/blog/_posts/2019-04-17-future-of-cloud-providers.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,12 @@
22
layout: blog
33
title: 'The Future of Cloud Providers in Kubernetes'
44
date: 2019-04-17
5+
author: >
6+
Andrew Sy Kim (VMware),
7+
Mike Crute (AWS),
8+
Walter Fender (Google)
59
---
610

7-
**Authors:** Andrew Sy Kim (VMware), Mike Crute (AWS), Walter Fender (Google)
8-
911
Approximately 9 months ago, the Kubernetes community agreed to form the Cloud Provider Special Interest Group (SIG). The justification was to have a single governing SIG to own and shape the integration points between Kubernetes and the many cloud providers it supported. A lot has been in motion since then and we’re here to share with you what has been accomplished so far and what we hope to see in the future.
1012

1113
## The Mission

‎content/en/blog/_posts/2019-04-19-Introducing-kube-iptables-tailer-Better-Networking-Visibility-in-Kubernetes-Clusters.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@ layout: blog
33
title: "Introducing kube-iptables-tailer: Better Networking Visibility in Kubernetes Clusters"
44
date: 2019-04-19
55
slug: introducing-kube-iptables-tailer
6+
author: >
7+
Saifuding Diliyaer (Box)
68
---
79

8-
**Authors:** Saifuding Diliyaer, Software Engineer, Box
9-
1010
At Box, we use Kubernetes to empower our engineers to own the whole lifecycle of their microservices. When it comes to networking, our engineers use Tigera’s [Project Calico](https://www.tigera.io/tigera-calico/) to declaratively manage network policies for their apps running in our Kubernetes clusters. App owners define a Calico policy in order to enable their Pods to send/receive network traffic, which is instantiated as iptables rules.
1111

1212
There may be times, however, when such network policy is missing or declared incorrectly by app owners. In this situation, the iptables rules will cause network packet drops between the affected Pods, which get logged in a file that is inaccessible to app owners. We needed a mechanism to seamlessly deliver alerts about those iptables packet drops based on their network policies to help app owners quickly diagnose the corresponding issues. To solve this, we developed a service called [kube-iptables-tailer](https://github.com/box/kube-iptables-tailer) to detect packet drops from iptables logs and report them as Kubernetes events. We are proud to open-source kube-iptables-tailer for you to utilize in your own cluster, regardless of whether you use Calico or other network policy tools.

‎content/en/blog/_posts/2019-04-24-Hardware-Accelerated-SSLTLS-Termination-in-Ingress-Controllers-using-Kubernetes-Device-Plugins-and-RuntimeClass.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
layout: blog
33
title: 'Hardware Accelerated SSL/TLS Termination in Ingress Controllers using Kubernetes Device Plugins and RuntimeClass'
44
date: 2019-04-24
5+
author: >
6+
Mikko Ylinen (Intel)
57
---
68

7-
**Authors:** Mikko Ylinen (Intel)
8-
99
## Abstract
1010

1111
A Kubernetes Ingress is a way to connect cluster services to the world outside the cluster. In order

‎content/en/blog/_posts/2019-04-26-latest-on-localization.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
layout: blog
33
title: 'How You Can Help Localize Kubernetes Docs'
44
date: 2019-04-26
5+
author: >
6+
Zach Corleissen (Linux Foundation)
57
---
68

7-
**Author: Zach Corleissen (Linux Foundation)**
8-
99
Last year we optimized the Kubernetes website for [hosting multilingual content](/blog/2018/11/08/kubernetes-docs-updates-international-edition/). Contributors responded by adding multiple new localizations: as of April 2019, Kubernetes docs are partially available in nine different languages, with six added in 2019 alone. You can see a list of available languages in the language selector at the top of each page.
1010

1111
By _partially available_, I mean that localizations are ongoing projects. They range from mostly complete ([Chinese docs for 1.12](https://v1-12.docs.kubernetes.io/zh-cn/)) to brand new (1.14 docs in [Portuguese](https://kubernetes.io/pt/)). If you're interested in helping an existing localization, read on!

0 commit comments

Comments
 (0)