[ja] Translate content/ja/docs/tasks/tools/install-kubectl-windows.md (#45486)

levi106 · web-flow · commit de98cc74a50f · 2024-04-12T07:10:10.000-07:00
* [ja] Translate content/ja/docs/tasks/tools/install-kubectl-windows.md

* remove revieweres
added a link to the minikube installation website
del command update
diff --git a/content/ja/docs/tasks/tools/included/_index.md b/content/ja/docs/tasks/tools/included/_index.md
@@ -0,0 +1,10 @@
+---
+title: "Tools Included"
+description: "メインのkubectl-installs-*.mdページに含まれるスニペット。"
+headless: true
+toc_hide: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
diff --git a/content/ja/docs/tasks/tools/included/kubectl-convert-overview.md b/content/ja/docs/tasks/tools/included/kubectl-convert-overview.md
@@ -0,0 +1,14 @@
+---
+title: "kubectl-convertの概要"
+description: >-
+  Kubernetes APIのあるバージョンから別のバージョンにマニフェストを変換することができるkubectlプラグイン。
+headless: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
+
+異なるAPIバージョン間でマニフェストを変換できる、Kubernetesコマンドラインツール`kubectl`のプラグインです。
+これは特に、新しいKubernetesのリリースで、非推奨ではないAPIバージョンにマニフェストを移行する場合に役に立ちます。
+詳細については[非推奨ではないAPIへの移行](/docs/reference/using-api/deprecation-guide/#migrate-to-non-deprecated-apis)を参照してください。
diff --git a/content/ja/docs/tasks/tools/included/kubectl-whats-next.md b/content/ja/docs/tasks/tools/included/kubectl-whats-next.md
@@ -0,0 +1,15 @@
+---
+title: "次の項目"
+description: "kubectlをインストールした後の次の項目。"
+headless: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
+
+* [Minikubeをインストールする](https://minikube.sigs.k8s.io/docs/start/)
+* クラスターの作成に関する詳細を[スタートガイド](/ja/docs/setup/)で確認する。
+* [アプリケーションを起動して公開する方法を学ぶ。](/ja/docs/tasks/access-application-cluster/service-access-application-cluster/)
+* あなたが作成していないクラスターにアクセスする必要がある場合は、[クラスターアクセスドキュメントの共有](/ja/docs/tasks/access-application-cluster/configure-access-multiple-clusters/)を参照してください。
+* [kubectlリファレンスドキュメント](/docs/reference/kubectl/kubectl/)を参照する
diff --git a/content/ja/docs/tasks/tools/included/optional-kubectl-configs-bash-linux.md b/content/ja/docs/tasks/tools/included/optional-kubectl-configs-bash-linux.md
@@ -0,0 +1,73 @@
+---
+title: "bash auto-completion on Linux"
+description: "Some optional configuration for bash auto-completion on Linux."
+headless: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
+
+### 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`).
+
+### Install bash-completion
+
+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
+source /usr/share/bash-completion/bash_completion
+```
+
+Reload your shell and verify that bash-completion is correctly installed by typing `type _init_completion`.
+
+### 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:
+
+{{< tabs name="kubectl_bash_autocompletion" >}}
+{{< tab name="User" codelang="bash" >}}
+echo 'source <(kubectl completion bash)' >>~/.bashrc
+{{< /tab >}}
+{{< tab name="System" codelang="bash" >}}
+kubectl completion bash | sudo tee /etc/bash_completion.d/kubectl > /dev/null
+sudo chmod a+r /etc/bash_completion.d/kubectl
+{{< /tab >}}
+{{< /tabs >}}
+
+If you have an alias for kubectl, you can extend shell completion to work with that alias:
+
+```bash
+echo 'alias k=kubectl' >>~/.bashrc
+echo 'complete -o default -F __start_kubectl k' >>~/.bashrc
+```
+
+{{< note >}}
+bash-completion sources all completion scripts in `/etc/bash_completion.d`.
+{{< /note >}}
+
+Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working.
+To enable bash autocompletion in current session of shell, source the ~/.bashrc file:
+
+```bash
+source ~/.bashrc
+```
diff --git a/content/ja/docs/tasks/tools/included/optional-kubectl-configs-bash-mac.md b/content/ja/docs/tasks/tools/included/optional-kubectl-configs-bash-mac.md
@@ -0,0 +1,109 @@
+---
+title: "bash auto-completion on macOS"
+description: "Some optional configuration for bash auto-completion on macOS."
+headless: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
+
+### 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.
+
+{{< 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).
+{{< /warning >}}
+
+### Upgrade Bash
+
+The instructions here assume you use Bash 4.1+. You can check your Bash's version by running:
+
+```bash
+echo $BASH_VERSION
+```
+
+If it is too old, you can install/upgrade it using Homebrew:
+
+```bash
+brew install bash
+```
+
+Reload your shell and verify that the desired version is being used:
+
+```bash
+echo $BASH_VERSION $SHELL
+```
+
+Homebrew usually installs it at `/usr/local/bin/bash`.
+
+### Install 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).
+{{< /note >}}
+
+You can test if you have bash-completion v2 already installed with `type _init_completion`.
+If not, you can install it with Homebrew:
+
+```bash
+brew install bash-completion@2
+```
+
+As stated in the output of this command, add the following to your `~/.bash_profile` file:
+
+```bash
+brew_etc="$(brew --prefix)/etc" && [[ -r "${brew_etc}/profile.d/bash_completion.sh" ]] && . "${brew_etc}/profile.d/bash_completion.sh"
+```
+
+Reload your shell and verify that bash-completion v2 is correctly installed with `type _init_completion`.
+
+### Enable kubectl autocompletion
+
+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:
+
+    ```bash
+    echo 'source <(kubectl completion bash)' >>~/.bash_profile
+    ```
+
+- Add the completion script to the `/usr/local/etc/bash_completion.d` directory:
+
+    ```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:
+
+    ```bash
+    echo 'alias k=kubectl' >>~/.bash_profile
+    echo 'complete -o default -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.
+
+   {{< 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.
+   {{< /note >}}
+
+In any case, after reloading your shell, kubectl completion should be working.
diff --git a/content/ja/docs/tasks/tools/included/optional-kubectl-configs-fish.md b/content/ja/docs/tasks/tools/included/optional-kubectl-configs-fish.md
@@ -0,0 +1,23 @@
+---
+title: "fish auto-completion"
+description: "Optional configuration to enable fish shell auto-completion."
+headless: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
+
+{{< note >}}
+Autocomplete for Fish requires kubectl 1.23 or later.
+{{< /note >}}
+
+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:
+
+```shell
+kubectl completion fish | source
+```
+
+After reloading your shell, kubectl autocompletion should be working.
diff --git a/content/ja/docs/tasks/tools/included/optional-kubectl-configs-pwsh.md b/content/ja/docs/tasks/tools/included/optional-kubectl-configs-pwsh.md
@@ -0,0 +1,28 @@
+---
+title: "PowerShellの自動補完"
+description: "PowerShellの自動補完に対するいくつかの補助的な設定。"
+headless: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
+
+PowerShellにおけるkubectlの補完スクリプトは`kubectl completion powershell`コマンドで生成できます。
+
+すべてのシェルセッションでこれを行うには、次の行を`$PROFILE`ファイルに追加します。
+
+```powershell
+kubectl completion powershell | Out-String | Invoke-Expression
+```
+
+このコマンドは、PowerShellを起動する度に自動補完のスクリプトを再生成します。
+生成されたスクリプトを直接`$PROFILE`ファイルに追加することもできます。
+
+生成されたスクリプトを`$PROFILE`ファイルに追加するためには、PowerShellのプロンプトで次の行を実行します:
+
+```powershell
+kubectl completion powershell >> $PROFILE
+```
+
+シェルをリロードした後、kubectlの自動補完が機能します。
diff --git a/content/ja/docs/tasks/tools/included/optional-kubectl-configs-zsh.md b/content/ja/docs/tasks/tools/included/optional-kubectl-configs-zsh.md
@@ -0,0 +1,28 @@
+---
+title: "zsh auto-completion"
+description: "Some optional configuration for zsh auto-completion."
+headless: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
+
+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:
+
+```zsh
+source <(kubectl completion zsh)
+```
+
+If you have an alias for kubectl, kubectl autocompletion will automatically work with it.
+
+After reloading your shell, kubectl autocompletion should be working.
+
+If you get an error like `2: command not found: compdef`, then add the following to the beginning of your `~/.zshrc` file:
+
+```zsh
+autoload -Uz compinit
+compinit
+```
diff --git a/content/ja/docs/tasks/tools/included/verify-kubectl.md b/content/ja/docs/tasks/tools/included/verify-kubectl.md
@@ -0,0 +1,46 @@
+---
+title: "kubectlの設定を検証する"
+description: "kubectlを検証する方法。"
+headless: true
+_build:
+  list: never
+  render: never
+  publishResources: false
+---
+
+kubectlがKubernetesクラスターを探索し接続するために、[kubeconfigファイル](/ja/docs/concepts/configuration/organize-cluster-access-kubeconfig/)が必要です。
+これは、[kube-up.sh](https://github.com/kubernetes/kubernetes/blob/master/cluster/kube-up.sh)によりクラスターを作成した際や、Minikubeクラスターを正常にデプロイした際に自動生成されます。
+デフォルトでは、kubectlの設定は`~/.kube/config`に格納されています。
+
+クラスターの状態を取得し、kubectlが適切に設定されていることを確認してください:
+
+```shell
+kubectl cluster-info
+```
+
+URLのレスポンスが表示されている場合は、kubectlはクラスターに接続するよう正しく設定されています。
+
+以下のようなメッセージが表示されている場合は、kubectlは正しく設定されていないか、Kubernetesクラスターに接続できていません。
+
+```
+The connection to the server <server-name:port> was refused - did you specify the right host or port?
+```
+
+たとえば、ラップトップ上(ローカル環境)でKubernetesクラスターを起動するような場合、[Minikube](https://minikube.sigs.k8s.io/docs/start/)などのツールを最初にインストールしてから、上記のコマンドを再実行する必要があります。
+
+kubectl cluster-infoがURLレスポンスを返したにもかかわらずクラスターにアクセスできない場合は、次のコマンドで設定が正しいことを確認してください:
+
+```shell
+kubectl cluster-info dump
+```
+
+### エラーメッセージ'No Auth Provider Found'のトラブルシューティング{#no-auth-provider-found}
+
+Kubernetes 1.26にて、kubectlは以下のクラウドプロバイダーが提供するマネージドKubernetesのビルトイン認証を削除しました。
+これらのプロバイダーは、クラウド固有の認証を提供するkubectlプラグインをリリースしています。
+手順については以下のプロバイダーのドキュメントを参照してください:
+
+* Azure AKS: [kubelogin plugin](https://azure.github.io/kubelogin/)
+* Google Kubernetes Engine: [gke-gcloud-auth-plugin](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#install_plugin)
+
+(この変更とは関係なく、他の理由で同じエラーメッセージが表示される可能性もあります。)
diff --git a/content/ja/docs/tasks/tools/install-kubectl-linux.md b/content/ja/docs/tasks/tools/install-kubectl-linux.md
diff --git a/content/ja/docs/tasks/tools/install-kubectl-macos.md b/content/ja/docs/tasks/tools/install-kubectl-macos.md
diff --git a/content/ja/docs/tasks/tools/install-kubectl-windows.md b/content/ja/docs/tasks/tools/install-kubectl-windows.md
