jiebi/CodeConvo huggingface dataset:
Change:
This is a Bug Report Problem: it seems that there is wrong indentation example- Proposed Solution: change to: path: / backend: serviceName: web servicePort: 8080 instead of: path: / backend: serviceName: web servicePort: 8080 Page to Update: Additional Information: This is the error thrown: $ kubectl apply -f example- error: error validating "example-": error validating data: [ValidationError([0]): unknown field "backend" in , ValidationError([0][0]): missing required field "backend" in ]; if you choose to ignorethese errors, turn validation off with --validate=false $
Thank you for your submission and have tried to fix it. /kind bug /language en /assign

Discussion:
1. Create `example-ingress.yaml` from the following file: <del> ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: example-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: hello-world.info http: paths: - path: / pathType: Prefix backend: service: name: web port: number: 8080 ``` </del> <ins> {{< codenew file="ingress/example-ingress.yaml" >}} </ins> 1. Create the Ingress resource by running the following command: ```shell <del> kubectl apply -f example-ingress.yaml </del> <ins> kubectl apply -f https://k8s.io/examples/ingress/example-ingress.yaml </ins> ``` Output:

<ins> apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: example-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: hello-world.info http: paths: - path: / pathType: Prefix backend: service: name: web port: number: 8080 </ins>  No newline at end of file
Change:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign

Discussion:
<ins> --- title: セットアップツールのリファレンス weight: 50 --- </ins>

<ins> --- title: "Kubeadm" weight: 10 no_list: true content_type: concept card: name: reference weight: 40 --- <img src="https://raw.githubusercontent.com/kubernetes/kubeadm/master/logos/stacked/color/kubeadm-stacked-color.png" align="right" width="150px">kubeadmは、`kubeadm init`や`kubeadm join`などのコマンドを提供するツールで、Kubernetesクラスターを構築する上でのベストプラクティスを反映した「近道」を提供するものとして開発されました。 kubeadmは実用最小限のクラスターをセットアップするための処理を実行します。設計上、kubeadmはブートストラップのみを行い、マシンのプロビジョニングは行いません。同様に、Kubernetesダッシュボード、モニタリングソリューション、クラウド向けのアドオンなど、あれば便利でもなくても支障のない各種アドオンのインストールも範囲外です。 その代わりに、高度な特定用途向けのツールはkubeadmをベースに構築されることが期待されています。理想的には、すべてのデプロイのベースとしてkubeadmを使用することで、適合テストに通るクラスターを簡単に作れるようになります。 ## インストール方法 kubeadmをインストールするには、[インストールガイド](/ja/docs/setup/production-environment/tools/kubeadm/install-kubeadm)を参照してください。 ## {{% heading "whatsnext" %}} * [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init)を使用して、Kubernetesのコントロールプレーンノードをブートストラップする * [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join)を使用して、Kubernetesのワーカーノードをブートストラップし、クラスターに参加させる * [kubeadm upgrade](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade)で、Kubernetesクラスターを新しいバージョンにアップグレードする * [kubeadm config](/docs/reference/setup-tools/kubeadm/kubeadm-config)を使用して、kubeadm v1.7.x以前で初期化されたクラスターを、`kubeadm upgrade`を利用できるように設定する * [kubeadm token](/docs/reference/setup-tools/kubeadm/kubeadm-token)で、`kubeadm join`のためのトークンを管理する * [kubeadm reset](/docs/reference/setup-tools/kubeadm/kubeadm-reset)を使用して、`kubeadm init`または`kubeadm join`でホストに行われた変更を元に戻す * [kubeadm version](/docs/reference/setup-tools/kubeadm/kubeadm-version)で、kubeadmのバージョンを表示する * [kubeadm alpha](/docs/reference/setup-tools/kubeadm/kubeadm-alpha)で、コミュニティからのフィードバックを集めるために有効にされた各種機能を試用する </ins>
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--CI/CD Pipeline utorials horribly out of date. Depends on kubernetes 1.6 Proposed Solution: I wish I had the time to work on this. Remove it or update it. Page to Update: Links to out of date tutirial: CI/CD Pipeline <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind cleanup /priority important-longterm /language en /help I recommend removing the section entirely, it is really out of date; also, even though the links are to external documentation the reference to Jenkins isn't really in the spirit of the policy.
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /kind cleanup /priority important-longterm /language en /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/retitle Tutorials overview links to outdated CI/CD Pipeline pages
/assign

Discussion:
* [Running ZooKeeper, A CP Distributed System](/docs/tutorials/stateful-application/zookeeper/) <del> ## CI/CD Pipeline * [Set Up a CI/CD Pipeline with Kubernetes Part 1: Overview](https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/5/set-cicd-pipeline-kubernetes-part-1-overview) * [Set Up a CI/CD Pipeline with a Jenkins Pod in Kubernetes (Part 2)](https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/6/set-cicd-pipeline-jenkins-pod-kubernetes-part-2) * [Run and Scale a Distributed Crossword Puzzle App with CI/CD on Kubernetes (Part 3)](https://www.linux.com/blog/learn/chapter/intro-to-kubernetes/2017/6/run-and-scale-distributed-crossword-puzzle-app-cicd-kubernetes-part-3) * [Set Up CI/CD for a Distributed Crossword Puzzle App on Kubernetes (Part 4)](https://www.linux.com/blog/learn/chapter/intro-to-kubernetes/2017/6/set-cicd-distributed-crossword-puzzle-app-kubernetes-part-4) </del> ## Clusters * [AppArmor](/docs/tutorials/clusters/apparmor/)
Change:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign

Discussion:
<ins> --- title: ドキュメントスタイルの概要 main_menu: true weight: 80 --- このセクション内のトピックでは、文章のスタイル、コンテンツの形式や構成、特にKubernetesのドキュメント特有のHugoカスタマイズの使用方法に関するガイダンスを提供します。 </ins>
Change:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
<ins> --- title: ドキュメントコンテンツガイド linktitle: コンテンツガイド content_type: concept weight: 10 --- <!-- overview --> このページでは、Kubernetesのドキュメント上のコンテンツのガイドラインを説明します。 許可されるコンテンツに関して疑問がある場合は、[Kubernetes Slack](https://slack.k8s.io/)の#sig-docsチャンネルに参加して質問してください！ Kubernetes Slackには、<https://slack.k8s.io/> から参加登録ができます。 Kubernetesドキュメントの新しいコンテンツの作成に関する情報については、[スタイルガイド](/docs/contribute/style/style-guide)に従ってください。 <!-- body --> ## 概要 ドキュメントを含むKubernetesのウェブサイトのソースは、[kubernetes/website](https://github.com/kubernetes/website)リポジトリに置かれています。 Kubernetesの主要なドキュメントは`kubernetes/website/content/<language_code>/docs`フォルダに置かれており、これらは[Kubernetesプロジェクト](https://github.com/kubernetes/kubernetes)を対象としています。 ## 許可されるコンテンツ Kubernetesのドキュメントにサードパーティーのコンテンツを掲載することが許されるのは、次の場合のみです。 - コンテンツがKubernetesプロジェクト内のソフトウェアのドキュメントとなる場合 - コンテンツがプロジェクト外のソフトウェアのドキュメントとなるが、Kubernetesを機能させるために必要である場合 - コンテンツがkubernetes.ioの正規のコンテンツであるか、他の場所の正規のコンテンツへのリンクである場合 ### サードパーティーのコンテンツ Kubernetesのドキュメントには、Kubernetesプロジェクト([kubernetes](https://github.com/kubernetes)および[kubernetes-sigs](https://github.com/kubernetes-sigs) GitHub organizationsに存在するプロジェクト)の適用例が含まれています。 Kubernetesプロジェクト内のアクティブなコンテンツへのリンクは常に許可されます。 Kubernetesを機能させるためには、一部サードパーティーのコンテンツが必要です。たとえば、コンテナランタイム(containerd、CRI-O、Docker)、[ネットワークポリシー](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/)(CNI plugin)、[Ingressコントローラー](/ja/docs/concepts/services-networking/ingress-controllers/)、[ロギング](/docs/concepts/cluster-administration/logging/)などです。 ドキュメント内で、Kubernetesプロジェクト外のサードパーティーのオープンソースソフトウェア(OSS)にリンクすることができるのは、Kubernetesを機能させるために必要な場合のみです。 ### 情報源が重複するコンテンツ 可能な限り、Kubernetesのドキュメントは正規の情報源にリンクするようにし、情報源が重複してしまうようなホスティングは行いません。 情報源が重複したコンテンツは、メンテナンスするために2倍の労力(あるいはそれ以上！)が必要になり、より早く情報が古くなってしまいます。 {{< note >}} あなたがKubernetesのプロジェクトのメンテナーであり、ドキュメントのホスティングに関して手助けが必要なときは、[Kubernetes Slackの#sig-docs](https://kubernetes.slack.com/messages/C1J0BPD2M/)で教えてください。 {{< /note >}} ### その他の情報 許可されるコンテンツに関して疑問がある場合は、[Kubernetes Slack](https://slack.k8s.io/)の#sig-docsチャンネルに参加して質問してください！ ## {{% heading "whatsnext" %}} * [スタイルガイド](/docs/contribute/style/style-guide)を読む </ins>
Change:
This is a clean-up request <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Pages such as use the for the term “API Server”. At the moment that shortcode hyperlinks to which then redirects to This is reference documentation and quite a lot to take in, especially for someone who is new to Kubernetes. I recommend updating the glossary term for “API Server” to hyperlink to Proposed Solution: Edit to . <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /language en /priority backlog /sig api-machinery /good-first-issue Notes: We try to . If you make this change to the English localization, feel free to suggest the equivalent change in other languages; it's a mechanical / repetitive update (a chore), but it also lets each localization team pick up approval tasks on their own cadence and using their own workflow. See for general guidance.
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a clean-up request <!-- See for guidance on writing an actionable issue description. --Problem: Pages such as use the for the term “API Server”. At the moment that shortcode hyperlinks to which then redirects to Edit to . <!--Kubernetes Version:--/kind cleanup /language en /priority backlog /sig api-machinery /good-first-issue We try to . If you make this change to the English localization, feel free to suggest the equivalent change in other languages; it's a mechanical / repetitive update (a chore), but it also lets each localization team pick up approval tasks on their own cadence and using their own workflow. See for general guidance. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
Hey , I have tried to work on this issue and opened a pull request. Kindly review it and suggest the necessary changes.

Discussion:
title: API server id: kube-apiserver date: 2018-04-12 <del> full_link: /docs/reference/generated/kube-apiserver/ </del> <ins> full_link: /docs/concepts/overview/components/#kube-apiserver </ins> short_description: > Control plane component that serves the Kubernetes API.
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Original text hast been kept along with translated text Proposed Solution: Delete original English text Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--<img width="863" alt="" src="https://user-"
Looks like the is still working even when being commented out. I have encountered this a hundred times when tidying up the Chinese localization, and this is one of the reasons I don't like this shortcode.
/assign

Discussion:
<!-- ### cloud-controller-manager <del> {{< glossary_definition term_id="cloud-controller-manager" length="short" >}} </del> The cloud-controller-manager only runs controllers that are specific to your cloud provider. If you are running Kubernetes on your own premises, or in a learning environment inside your own PC, the cluster does not have a cloud controller manager.

--> ### cloud-controller-manager <ins> {{< glossary_definition term_id="cloud-controller-manager" length="short" >}} </ins> `cloud-controller-manager` 进运行特定于云平台的控制回路。 如果你在自己的环境中运行 Kubernetes，或者在本地计算机中运行学习环境， 所部属的环境中不需要云控制器管理器。
Change:
This is a Bug Report Links within the tab component are not displaying using the site link color. Problem: The color of links within tab components is defaulting to . The link is inheriting the color value from jquery-ui- Proposed Solution: Update the style for ui-widget-content -a Page to Update: Start by looking at . Examples: See link in Flatcar Container Linux tab in Look as the "vSphere" tab at the bottom of the page.
Related to PR .
/kind bug /priority backlog /area web-development Feel free to reprioritize
/assign

Discussion:
body { background-color: white; <ins> a { color: $blue; } </ins> } section {

padding-top: 2rem !important; } } <ins> .ui-widget { font-family: inherit; font-size: inherit; } .ui-widget-content a { color: $blue; } </ins> } section {
Change:
This is a Feature Request What would you like to be Translate docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes/ into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
<ins> --- title: Windowsノードのアップグレード min-kubernetes-server-version: 1.17 content_type: task weight: 40 --- <!-- overview --> {{< feature-state for_k8s_version="v1.18" state="beta" >}} このページでは、[kubeadmで作られた](/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes)Windowsノードをアップグレードする方法について説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} * [残りのkubeadmクラスターをアップグレードするプロセス](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade)を理解します。 Windowsノードをアップグレードする前にコントロールプレーンノードをアップグレードしたいと思うかもしれません。 <!-- steps --> ## ワーカーノードをアップグレード ### kubeadmをアップグレード 1.  Windowsノードから、kubeadmをアップグレードします。: ```powershell # {{< param "fullversion" >}}を目的のバージョンに置き換えます curl.exe -Lo C:kkubeadm.exe https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubeadm.exe ``` ### ノードをドレインする 1.  Kubernetes APIにアクセスできるマシンから、 ノードをスケジュール不可としてマークして、ワークロードを削除することでノードのメンテナンスを準備します: ```shell # <node-to-drain>をドレインするノードの名前に置き換えます kubectl drain <node-to-drain> --ignore-daemonsets ``` このような出力結果が表示されるはずです: ``` node/ip-172-31-85-18 cordoned node/ip-172-31-85-18 drained ``` ### kubeletの構成をアップグレード 1. Windowsノードから、次のコマンドを呼び出して新しいkubelet構成を同期します: ```powershell kubeadm upgrade node ``` ### kubeletをアップグレード 1.  Windowsノードから、kubeletをアップグレードして再起動します: ```powershell stop-service kubelet curl.exe -Lo C:kkubelet.exe https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubelet.exe restart-service kubelet ``` ### ノードをオンライン状態に 1.  Kubernetes APIにアクセスできるマシンから、 スケジュール可能としてマークして、ノードをオンラインに戻します: ```shell # <node-to-drain>をノードの名前に置き換えます kubectl uncordon <node-to-drain> ``` ### kube-proxyをアップグレード 1. Kubernetes APIにアクセスできるマシンから、次を実行します、 もう一度{{< param "fullversion" >}}を目的のバージョンに置き換えます: ```shell curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/kube-proxy.yml | sed 's/VERSION/{{< param "fullversion" >}}/g' | kubectl apply -f - ``` </ins>
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Line 496: the line should be removed completely Techniques for spreading traffic across failure domains differs between cloud providers. Please check the documentation of the relevant for details. for details on deploying Ingress in a federated cluster. Proposed Solution: Line 496: the line should be removed completely Techniques for spreading traffic across failure domains differs between cloud providers. Please check the documentation of the relevant for details. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/kind bug /language en /priority backlog

Discussion:
Techniques for spreading traffic across failure domains differs between cloud providers. Please check the documentation of the relevant [Ingress controller](/docs/concepts/services-networking/ingress-controllers) for details. <del> for details on deploying Ingress in a federated cluster. </del> ## Alternatives
Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Broken layout for tabs on "Container runtimes" page as below. ! Proposed Solution: TBD Page to Update: /language ko <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/retitle Broken layout for tabs on "Container runtimes" page in Korean
This problem is due to incorrect tab code. We should fix this like the below: (Line 71, 125, 126, 180) to
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Hey folks, I'm happy to help you with this /assign

Discussion:
시스템에 도커를 설치하기 위해서 아래의 커맨드들을 사용한다. {{< tabs name="tab-cri-docker-installation" >}} <del> {{< tab name="Ubuntu 16.04+" >}} </del> <ins> {{% tab name="Ubuntu 16.04+" %}} </ins> ```shell # (도커 CE 설치)

systemctl daemon-reload systemctl restart docker ``` <del> {{< /tab >}} {{< tab name="CentOS/RHEL 7.4+" >}} </del> <ins> {{% /tab %}} {{% tab name="CentOS/RHEL 7.4+" %}} </ins> ```shell # (도커 CE 설치)

systemctl daemon-reload systemctl restart docker ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> {{< /tabs >}} 부팅 시 도커 서비스를 시작하려면, 다음 명령을 실행한다.

``` {{< tabs name="tab-cri-cri-o-installation" >}} <del> {{< tab name="Debian" >}} </del> <ins> {{% tab name="Debian" %}} </ins> ```shell # Debian 개발 배포본(Unstable/Sid)

```shell sudo apt-get install cri-o-1.17 ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> <del> {{< tab name="Ubuntu 18.04, 19.04 and 19.10" >}} </del> <ins> {{% tab name="Ubuntu 18.04, 19.04 and 19.10" %}} </ins> ```shell #  패키지 리포지터리 설정

# CRI-O 설치 sudo apt-get install cri-o-1.17 ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> <del> {{< tab name="CentOS/RHEL 7.4+" >}} </del> <ins> {{% tab name="CentOS/RHEL 7.4+" %}} </ins> ```shell # 선행 조건 설치

yum install -y cri-o ``` <del> {{< tab name="openSUSE Tumbleweed" >}} </del> <ins> {{% tab name="openSUSE Tumbleweed" %}} </ins> ```shell sudo zypper install cri-o ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> {{< /tabs >}} ### CRI-O 시작

### containerd 설치 {{< tabs name="tab-cri-containerd-installation" >}} <del> {{< tab name="Ubuntu 16.04" >}} </del> <ins> {{% tab name="Ubuntu 16.04" %}} </ins> ```shell # (containerd 설치)

# containerd 재시작 systemctl restart containerd ``` <del> {{< /tab >}} {{< tab name="CentOS/RHEL 7.4+" >}} </del> <ins> {{% /tab %}} {{% tab name="CentOS/RHEL 7.4+" %}} </ins> ```shell # (containerd 설치)

# containerd 재시작 systemctl restart containerd ``` <del> {{< /tab >}} </del> <ins> {{% /tab %}} </ins> {{< /tabs >}} ### systemd
Change:
I found the references to and v1alpha2 to be confusing since the configuration that follow were v1beta1. Perhaps it would make sense to remove the alpha1/2 references entirely? !

Discussion:
You can specify scheduling profiles by running `kube-scheduler --config <filename>`, using the component config APIs <del> ([`v1alpha1`](https://pkg.go.dev/k8s.io/kube-scheduler@v0.18.0/config/v1alpha1?tab=doc#KubeSchedulerConfiguration) or [`v1alpha2`](https://pkg.go.dev/k8s.io/kube-scheduler@v0.18.0/config/v1alpha2?tab=doc#KubeSchedulerConfiguration)). The `v1alpha2` API allows you to configure kube-scheduler to run [multiple profiles](#multiple-profiles). </del> <ins> ([`v1beta1`](https://pkg.go.dev/k8s.io/kube-scheduler@v0.19.0/config/v1beta1?tab=doc#KubeSchedulerConfiguration)). </ins> A minimal configuration looks as follows:
Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Add a short link for the . Why is this needed A short link, eg , is easier to type and remember. Comments I recommend not using the usual 301 redirect here because it's not a permanent move. Instead, use a 307 redirect. Should we repeat this for localizations? Eg In the cheat sheet page itself, consider mentioning the short link in the text of the page. /kind feature /language en
/priority backlog
/assign
Thanks !

Discussion:
/docs/user-guide/kubectl/     /docs/reference/generated/kubectl/kubectl-options/ /docs/user-guide/kubectl-conventions/     /docs/reference/kubectl/conventions/ /docs/user-guide/kubectl-cheatsheet/     /docs/reference/kubectl/cheatsheet/ <ins> /cheatsheet /docs/reference/kubectl/cheatsheet/ 302 </ins> /docs/user-guide/kubectl/kubectl_*/     /docs/reference/generated/kubectl/kubectl-commands#:splat 301 /docs/user-guide/labels/     /docs/concepts/overview/working-with-objects/labels/ 301 /docs/user-guide/liveness/     /docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ 301
Change:
This is a Bug Report Problem: is missing in Chinese version. Proposed Solution: Add content/zh/docs/setup/learning- Page to Update: content/zh/docs/setup/learning- content/zh/docs/setup/learning-
/language zh /assign

Discussion:
<ins> --- title: 使用 Kind 安装 Kubernetes weight: 40 content_type: concept --- <!-- overview --> <!-- Kind is a tool for running local Kubernetes clusters using Docker container "nodes". --> Kind 是一个使用 Docker 容器“节点”运行本地 Kubernetes 集群的工具。 <!-- body --> <!-- ## Installation See [Installing Kind](https://kind.sigs.k8s.io/docs/user/quick-start/). --> ## 安装  {#installation} 参见[安装 Kind ](https://kind.sigs.k8s.io/docs/user/quick-start/)。 </ins>

--- title: 使用 Minikube 安装 Kubernetes <ins> weight: 30 </ins> content_type: concept --- <!--