Switch language name 'zh' to 'zh-cn'

This is the first step to rename 'zh' to 'zh-cn'. There are several reasons why we rename the language name. - The upstream docsy theme changed the language name, leading to many warnings during site build; The side-effect is that the i18n strings are no longer working. - We believe renaming the language is the right thing to do, because this move can make room for other variants of Chinese language, such as 'zh-tw', 'zh-sg' etc. There would be several follow-ups to this PR, such as fixing the intra-site links, adding redirects etc. We will lock up changes to zh/zh-cn pages for the moment, until this one gets in. This PR is based on commit cdad0a7342.
2022-06-10 20:25:27 +08:00
parent 3d345b1816
commit c52818c03d
1347 changed files with 8 additions and 6 deletions
@@ -0,0 +1,14 @@
+---
+title: "内含的工具"
+description: "在页面 kubectl-installs-*.md 中包含的代码片段"
+headless: true
+toc_hide: true
+---
+<!-- 
+---
+title: "Tools Included"
+description: "Snippets to be included in the main kubectl-installs-*.md pages."
+headless: true
+toc_hide: true
+---
+-->
@@ -0,0 +1,24 @@
+---
+title: "kubectl-convert 概述"
+description: >-
+  一个 kubectl 插件，允许你将清单从一个 Kubernetes API 版本转换到不同的版本。
+headless: true
+---
+<!--
+---
+title: "kubectl-convert overview"
+description: >-
+  A kubectl plugin that allows you to convert manifests from one version
+  of a Kubernetes API to a different version.
+headless: true
+---
+-->
+
+<!--
+A plugin for Kubernetes command-line tool `kubectl`, which allows you to convert manifests between different API
+versions. This can be particularly helpful to migrate manifests to a non-deprecated api version with newer Kubernetes release.
+For more info, visit [migrate to non deprecated apis](/docs/reference/using-api/deprecation-guide/#migrate-to-non-deprecated-apis)
+-->
+一个 Kubernetes 命令行工具 `kubectl` 的插件，允许你将清单在不同 API 版本间转换。
+这对于将清单迁移到新的 Kubernetes 发行版上未被废弃的 API 版本时尤其有帮助。
+更多信息请访问 [迁移到非弃用 API](/zh/docs/reference/using-api/deprecation-guide/#migrate-to-non-deprecated-apis)
@@ -0,0 +1,27 @@
+---
+title: "后续内容"
+description: "安装 kubectl 之后，还可以做些什么？"
+headless: true
+---
+<!-- 
+---
+title: "What's next?"
+description: "What's next after installing kubectl."
+headless: true
+---
+-->
+
+<!-- 
+* [Install Minikube](https://minikube.sigs.k8s.io/docs/start/)
+* See the [getting started guides](/docs/setup/) for more about creating clusters.
+* [Learn how to launch and expose your application.](/docs/tasks/access-application-cluster/service-access-application-cluster/)
+* If you need access to a cluster you didn't create, see the
+  [Sharing Cluster Access document](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/).
+* Read the [kubectl reference docs](/docs/reference/kubectl/kubectl/)
+-->
+* [安装 Minikube](https://minikube.sigs.k8s.io/docs/start/)
+* 有关创建集群的更多信息，请参阅[入门指南](/zh/docs/setup/).
+* [学习如何启动并对外公开你的应用程序。](/zh/docs/tasks/access-application-cluster/service-access-application-cluster/)
+* 如果你需要访问其他人创建的集群，请参阅
+  [共享集群接入文档](/zh/docs/tasks/access-application-cluster/configure-access-multiple-clusters/).
+* 阅读 [kubectl 参考文档](/zh/docs/reference/kubectl/kubectl/)
@@ -0,0 +1,102 @@
+---
+title: "Linux 系统中的 bash 自动补全功能"
+description: "Linux 系统中 bash 自动补全功能的一些可选配置。"
+headless: true
+---
+<!-- 
+---
+title: "bash auto-completion on Linux"
+description: "Some optional configuration for bash auto-completion on Linux."
+headless: true
+---
+-->
+
+<!-- 
+### Introduction
+-->
+### 简介 {#introduction}
+
+<!-- 
+The kubectl completion script for Bash can be generated with the command `kubectl completion bash`. Sourcing the completion script in your shell enables kubectl autocompletion.
+
+However, the completion script depends on [**bash-completion**](https://github.com/scop/bash-completion), which means that you have to install this software first (you can test if you have bash-completion already installed by running `type _init_completion`).
+-->
+kubectl 的 Bash 补全脚本可以用命令 `kubectl completion bash` 生成。
+在 shell 中导入（Sourcing）补全脚本，将启用 kubectl 自动补全功能。
+
+然而，补全脚本依赖于工具 [**bash-completion**](https://github.com/scop/bash-completion)，
+所以要先安装它（可以用命令 `type _init_completion` 检查 bash-completion 是否已安装）。
+
+<!-- 
+### Install bash-completion
+-->
+### 安装 bash-completion {#install-bash-comletion}
+
+<!-- 
+bash-completion is provided by many package managers (see [here](https://github.com/scop/bash-completion#installation)). You can install it with `apt-get install bash-completion` or `yum install bash-completion`, etc.
+
+The above commands create `/usr/share/bash-completion/bash_completion`, which is the main script of bash-completion. Depending on your package manager, you have to manually source this file in your `~/.bashrc` file.
+
+To find out, reload your shell and run `type _init_completion`. If the command succeeds, you're already set, otherwise add the following to your `~/.bashrc` file:
+-->
+很多包管理工具均支持 bash-completion（参见[这里](https://github.com/scop/bash-completion#installation)）。
+可以通过 `apt-get install bash-completion` 或 `yum install bash-completion` 等命令来安装它。
+
+上述命令将创建文件 `/usr/share/bash-completion/bash_completion`，它是 bash-completion 的主脚本。
+依据包管理工具的实际情况，你需要在 `~/.bashrc` 文件中手工导入此文件。
+
+要查看结果，请重新加载你的 shell，并运行命令 `type _init_completion`。
+如果命令执行成功，则设置完成，否则将下面内容添加到文件 `~/.bashrc` 中：
+
+```bash
+source /usr/share/bash-completion/bash_completion
+```
+
+<!-- 
+Reload your shell and verify that bash-completion is correctly installed by typing `type _init_completion`.
+-->
+重新加载 shell，再输入命令 `type _init_completion` 来验证 bash-completion 的安装状态。
+
+<!-- 
+### Enable kubectl autocompletion
+-->
+### 启动 kubectl 自动补全功能 {#enable-kubectl-autocompletion}
+
+#### Bash
+
+<!-- 
+You now need to ensure that the kubectl completion script gets sourced in all your shell sessions. There are two ways in which you can do this:
+-->
+你现在需要确保一点：kubectl 补全脚本已经导入（sourced）到 shell 会话中。
+可以通过以下两种方法进行设置：
+
+{{< tabs name="kubectl_bash_autocompletion" >}}
+{{{< tab name="当前用户" codelang="bash" >}}
+echo 'source <(kubectl completion bash)' >>~/.bashrc
+{{< /tab >}}
+{{< tab name="系统全局" codelang="bash" >}}
+kubectl completion bash | sudo tee /etc/bash_completion.d/kubectl > /dev/null
+{{< /tab >}}}
+{{< /tabs >}}
+
+<!-- 
+If you have an alias for kubectl, you can extend shell completion to work with that alias:
+-->
+如果 kubectl 有关联的别名，你可以扩展 shell 补全来适配此别名：
+
+```bash
+echo 'alias k=kubectl' >>~/.bashrc
+echo 'complete -F __start_kubectl k' >>~/.bashrc
+```
+
+{{< note >}}
+<!-- 
+bash-completion sources all completion scripts in `/etc/bash_completion.d`.
+-->
+bash-completion 负责导入 `/etc/bash_completion.d` 目录中的所有补全脚本。
+{{< /note >}}
+
+<!-- 
+Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working.
+-->
+两种方式的效果相同。重新加载 shell 后，kubectl 自动补全功能即可生效。
@@ -0,0 +1,174 @@
+---
+title: "macOS 系统上的 bash 自动补全"
+description: "在 macOS 上实现 Bash 自动补全的一些可选配置。"
+headless: true
+---
+<!-- 
+title: "bash auto-completion on macOS"
+description: "Some optional configuration for bash auto-completion on macOS."
+headless: true
+ -->
+
+<!-- 
+### Introduction
+-->
+### 简介 
+
+<!-- 
+The kubectl completion script for Bash can be generated with `kubectl completion bash`. Sourcing this script in your shell enables kubectl completion.
+
+However, the kubectl completion script depends on [**bash-completion**](https://github.com/scop/bash-completion) which you thus have to previously install.
+-->
+kubectl 的 Bash 补全脚本可以通过 `kubectl completion bash` 命令生成。
+在你的 shell 中导入（Sourcing）这个脚本即可启用补全功能。
+
+此外，kubectl 补全脚本依赖于工具 [**bash-completion**](https://github.com/scop/bash-completion)，
+所以你必须先安装它。
+
+{{< warning>}}
+<!-- 
+There are two versions of bash-completion, v1 and v2. V1 is for Bash 3.2 (which is the default on macOS), and v2 is for Bash 4.1+. The kubectl completion script **doesn't work** correctly with bash-completion v1 and Bash 3.2. It requires **bash-completion v2** and **Bash 4.1+**. Thus, to be able to correctly use kubectl completion on macOS, you have to install and use Bash 4.1+ ([*instructions*](https://itnext.io/upgrading-bash-on-macos-7138bd1066ba)). The following instructions assume that you use Bash 4.1+ (that is, any Bash version of 4.1 or newer).
+-->
+bash-completion 有两个版本：v1 和 v2。v1 对应 Bash3.2（也是 macOS 的默认安装版本），v2 对应 Bash 4.1+。
+kubectl 的补全脚本**无法适配** bash-completion v1 和 Bash 3.2。
+必须为它配备  **bash-completion v2** 和 **Bash 4.1+**。
+有鉴于此，为了在 macOS 上使用 kubectl 补全功能，你必须要安装和使用 Bash 4.1+
+([*说明*](https://itnext.io/upgrading-bash-on-macos-7138bd1066ba))。
+后续说明假定你用的是 Bash 4.1+（也就是 Bash 4.1 或更新的版本）
+{{< /warning >}}
+
+<!-- 
+### Upgrade Bash
+-->
+### 升级 Bash
+
+<!-- 
+The instructions here assume you use Bash 4.1+. You can check your Bash's version by running:
+-->
+后续说明假定你已使用 Bash 4.1+。你可以运行以下命令检查 Bash 版本：
+
+```bash
+echo $BASH_VERSION
+```
+
+<!-- 
+If it is too old, you can install/upgrade it using Homebrew:
+-->
+如果版本太旧，可以用 Homebrew 安装/升级：
+
+```bash
+brew install bash
+```
+
+<!-- 
+Reload your shell and verify that the desired version is being used:
+-->
+重新加载 shell，并验证所需的版本已经生效：
+
+```bash
+echo $BASH_VERSION $SHELL
+```
+
+<!-- 
+Homebrew usually installs it at `/usr/local/bin/bash`.
+-->
+Homebrew 通常把它安装为 `/usr/local/bin/bash`。
+
+<!-- 
+### Install bash-completion
+-->
+### 安装 bash-completion
+
+
+{{< note >}}
+<!-- 
+As mentioned, these instructions assume you use Bash 4.1+, which means you will install bash-completion v2 (in contrast to Bash 3.2 and bash-completion v1, in which case kubectl completion won't work).
+-->
+如前所述，本说明假定你使用的 Bash 版本为 4.1+，这意味着你要安装 bash-completion v2
+（不同于 Bash 3.2 和 bash-completion v1，kubectl 的补全功能在该场景下无法工作）。
+{{< /note >}}
+
+<!-- 
+You can test if you have bash-completion v2 already installed with `type _init_completion`. If not, you can install it with Homebrew:
+-->
+你可以用命令 `type _init_completion` 测试 bash-completion v2 是否已经安装。
+如未安装，用 Homebrew 来安装它：
+
+```bash
+brew install bash-completion@2
+```
+
+<!-- 
+As stated in the output of this command, add the following to your `~/.bash_profile` file:
+-->
+如命令的输出信息所显示的，将如下内容添加到文件 `~/.bash_profile` 中：
+
+```bash
+export BASH_COMPLETION_COMPAT_DIR="/usr/local/etc/bash_completion.d"
+[[ -r "/usr/local/etc/profile.d/bash_completion.sh" ]] && . "/usr/local/etc/profile.d/bash_completion.sh"
+```
+
+<!-- 
+Reload your shell and verify that bash-completion v2 is correctly installed with `type _init_completion`.
+-->
+重新加载 shell，并用命令 `type _init_completion` 验证 bash-completion v2 已经恰当的安装。
+
+<!-- 
+### Enable kubectl autocompletion
+-->
+### 启用 kubectl 自动补全功能
+
+<!-- 
+You now have to ensure that the kubectl completion script gets sourced in all your shell sessions. There are multiple ways to achieve this:
+
+- Source the completion script in your `~/.bash_profile` file:
+-->
+你现在需要确保在所有的 shell 环境中均已导入（sourced） kubectl 的补全脚本，
+有若干种方法可以实现这一点：
+
+- 在文件 `~/.bash_profile` 中导入（Source）补全脚本：
+
+    ```bash
+    echo 'source <(kubectl completion bash)' >>~/.bash_profile
+    ```
+
+<!-- 
+- Add the completion script to the `/usr/local/etc/bash_completion.d` directory:
+-->
+- 将补全脚本添加到目录 `/usr/local/etc/bash_completion.d` 中：
+
+    ```bash
+    kubectl completion bash >/usr/local/etc/bash_completion.d/kubectl
+    ```
+
+<!-- 
+- If you have an alias for kubectl, you can extend shell completion to work with that alias:
+-->
+- 如果你为 kubectl 定义了别名，则可以扩展 shell 补全来兼容该别名：
+
+    ```bash
+    echo 'alias k=kubectl' >>~/.bash_profile
+    echo 'complete -F __start_kubectl k' >>~/.bash_profile
+    ```
+
+<!-- 
+- If you installed kubectl with Homebrew (as explained [here](/docs/tasks/tools/install-kubectl-macos/#install-with-homebrew-on-macos)), then the kubectl completion script should already be in `/usr/local/etc/bash_completion.d/kubectl`. In that case, you don't need to do anything.
+-->
+- 如果你是用 Homebrew 安装的 kubectl（如
+  [此页面](/zh/docs/tasks/install-with-homebrew-on-macos/#install-with-homebrew-on-macos)
+  所描述），则kubectl 补全脚本应该已经安装到目录 `/usr/local/etc/bash_completion.d/kubectl`
+  中了。这种情况下，你什么都不需要做。
+
+  {{< note >}}
+  <!-- 
+  The Homebrew installation of bash-completion v2 sources all the files in the `BASH_COMPLETION_COMPAT_DIR` directory, that's why the latter two methods work.
+  -->
+  用 Hommbrew 安装的 bash-completion v2 会初始化 目录 `BASH_COMPLETION_COMPAT_DIR`
+  中的所有文件，这就是后两种方法能正常工作的原因。
+  {{< /note >}}
+
+<!-- 
+In any case, after reloading your shell, kubectl completion should be working.
+-->
+总之，重新加载 shell 之后，kubectl 补全功能将立即生效。
+
@@ -0,0 +1,31 @@
+---
+title: "fish 自动补全"
+description: "启用 fish 自动补全的可选配置。"
+headless: true
+---
+<!--
+---
+title: "fish auto-completion"
+description: "Optional configuration to enable fish shell auto-completion."
+headless: true
+---
+-->
+
+<!--
+The kubectl completion script for Fish can be generated with the command `kubectl completion fish`. Sourcing the completion script in your shell enables kubectl autocompletion.
+
+To do so in all your shell sessions, add the following line to your `~/.config/fish/config.fish` file:
+-->
+kubectl 通过命令 `kubectl completion fish` 生成 Fish 自动补全脚本。
+在 shell 中导入（Sourcing）该自动补全脚本，将启动 kubectl 自动补全功能。
+
+为了在所有的 shell 会话中实现此功能，请将下面内容加入到文件 `~/.config/fish/config.fish` 中。
+
+```shell
+kubectl completion fish | source
+```
+
+<!--
+After reloading your shell, kubectl autocompletion should be working.
+-->
+重新加载 shell 后，kubectl 自动补全功能将立即生效。
@@ -0,0 +1,44 @@
+---
+title: "PowerShell 自动补全"
+description: "powershell 自动补全的一些可选配置。"
+headless: true
+---
+<!--
+---
+title: "PowerShell auto-completion"
+description: "Some optional configuration for powershell auto-completion."
+headless: true
+---
+-->
+
+<!--
+The kubectl completion script for PowerShell can be generated with the command `kubectl completion powershell`.
+
+To do so in all your shell sessions, add the following line to your `$PROFILE` file:
+-->
+使用命令 `kubectl completion powershell` 生成 PowerShell 的 kubectl 自动补全脚本。
+
+如果需要自动补全在所有 shell 会话中生效，请将以下命令添加到 `$PROFILE` 文件中：
+
+```powershell
+kubectl completion powershell | Out-String | Invoke-Expression
+```
+
+<!--
+This command will regenerate the auto-completion script on every PowerShell start up. You can also add the generated script directly to your `$PROFILE` file.
+-->
+此命令将在每次 PowerShell 启动时重新生成自动补全脚本。你还可以将生成的自动补全脚本添加到 `$PROFILE` 文件中。
+
+<!--
+To add the generated script to your `$PROFILE` file, run the following line in your powershell prompt:
+-->
+如果需要将自动补全脚本直接添加到 `$PROFILE` 文件中，请在 PowerShell 终端运行以下命令：
+
+```powershell
+kubectl completion powershell >> $PROFILE
+```
+
+<!--
+After reloading your shell, kubectl autocompletion should be working.
+-->
+完成上述操作后重启 shell，kubectl的自动补全就可以工作了。
@@ -0,0 +1,45 @@
+---
+title: "zsh 自动补全"
+description: "zsh 自动补全的一些可选配置"
+headless: true
+---
+<!-- 
+---
+title: "zsh auto-completion"
+description: "Some optional configuration for zsh auto-completion."
+headless: true
+---
+-->
+
+<!-- 
+The kubectl completion script for Zsh can be generated with the command `kubectl completion zsh`. Sourcing the completion script in your shell enables kubectl autocompletion.
+
+To do so in all your shell sessions, add the following to your `~/.zshrc` file:
+-->
+kubectl 通过命令 `kubectl completion zsh` 生成 Zsh 自动补全脚本。
+在 shell 中导入（Sourcing）该自动补全脚本，将启动 kubectl 自动补全功能。
+
+为了在所有的 shell 会话中实现此功能，请将下面内容加入到文件 `~/.zshrc` 中。
+
+```zsh
+source <(kubectl completion zsh)
+```
+
+<!-- 
+If you have an alias for kubectl, kubectl autocompletion will automatically work with it.
+-->
+如果你为 kubectl 定义了别名，kubectl 自动补全将自动使用它。
+
+<!-- 
+After reloading your shell, kubectl autocompletion should be working.
+
+If you get an error like `complete:13: command not found: compdef`, then add the following to the beginning of your `~/.zshrc` file:
+If you get an error like `2: command not found: compdef`, then add the following to the beginning of your `~/.zshrc` file:
+-->
+重新加载 shell 后，kubectl 自动补全功能将立即生效。
+
+如果你收到 `2: command not found: compdef` 这样的错误提示，那请将下面内容添加到 `~/.zshrc` 文件的开头：
+```zsh
+autoload -Uz compinit
+compinit
+```
@@ -0,0 +1,62 @@
+---
+title: "验证 kubectl 的安装效果"
+description: "如何验证 kubectl。"
+headless: true
+---
+<!-- 
+---
+title: "verify kubectl install"
+description: "How to verify kubectl."
+headless: true
+---
+ -->
+
+<!-- 
+In order for kubectl to find and access a Kubernetes cluster, it needs a
+[kubeconfig file](/docs/concepts/configuration/organize-cluster-access-kubeconfig/),
+which is created automatically when you create a cluster using
+[kube-up.sh](https://github.com/kubernetes/kubernetes/blob/master/cluster/kube-up.sh)
+or successfully deploy a Minikube cluster.
+By default, kubectl configuration is located at `~/.kube/config`.
+
+Check that kubectl is properly configured by getting the cluster state:
+ -->
+为了让 kubectl 能发现并访问 Kubernetes 集群，你需要一个
+[kubeconfig 文件](/zh/docs/concepts/configuration/organize-cluster-access-kubeconfig/)，
+该文件在
+[kube-up.sh](https://github.com/kubernetes/kubernetes/blob/master/cluster/kube-up.sh)
+创建集群时，或成功部署一个 Miniube 集群时，均会自动生成。
+通常，kubectl 的配置信息存放于文件 `~/.kube/config` 中。
+
+通过获取集群状态的方法，检查是否已恰当的配置了 kubectl：
+
+```shell
+kubectl cluster-info
+```
+
+<!-- 
+If you see a URL response, kubectl is correctly configured to access your cluster.
+
+If you see a message similar to the following, kubectl is not configured correctly or is not able to connect to a Kubernetes cluster.
+ -->
+如果返回一个 URL，则意味着 kubectl 成功的访问到了你的集群。
+
+如果你看到如下所示的消息，则代表 kubectl 配置出了问题，或无法连接到 Kubernetes 集群。
+
+```
+The connection to the server <server-name:port> was refused - did you specify the right host or port?
+（访问 <server-name:port> 被拒绝 - 你指定的主机和端口是否有误？）
+```
+
+<!-- 
+For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like Minikube to be installed first and then re-run the commands stated above.
+
+If kubectl cluster-info returns the url response but you can't access your cluster, to check whether it is configured properly, use:
+ -->
+例如，如果你想在自己的笔记本上（本地）运行 Kubernetes 集群，你需要先安装一个 Minikube 这样的工具，然后再重新运行上面的命令。
+
+如果命令 `kubectl cluster-info` 返回了 url，但你还不能访问集群，那可以用以下命令来检查配置是否妥当：
+
+```shell
+kubectl cluster-info dump
+```