From 67bea6b7b6e0605829ca348139c9ddd4b68a602f Mon Sep 17 00:00:00 2001 From: Derek Nola Date: Wed, 2 Oct 2024 10:33:59 -0700 Subject: [PATCH] Fix old web links Signed-off-by: Derek Nola --- docs/datastore/datastore.md | 2 +- docs/faq.md | 2 +- docs/installation/airgap.md | 2 +- docs/installation/registry-mirror.md | 2 +- docs/networking/distributed-multicloud.md | 2 +- docs/security/hardening-guide.md | 2 +- docs/security/self-assessment-1.23.md | 2 +- docs/security/self-assessment-1.24.md | 2 +- docs/security/self-assessment-1.7.md | 2 +- docs/security/self-assessment-1.8.md | 2 +- docs/upgrades/automated.md | 2 +- docs/upgrades/manual.md | 2 +- .../current/datastore/datastore.md | 2 +- i18n/ja/docusaurus-plugin-content-docs/current/faq.md | 2 +- .../current/installation/airgap.md | 2 +- .../current/installation/registry-mirror.md | 2 +- .../current/networking/distributed-multicloud.md | 2 +- .../current/security/hardening-guide.md | 2 +- .../current/security/self-assessment-1.23.md | 2 +- .../current/security/self-assessment-1.24.md | 2 +- .../current/security/self-assessment-1.7.md | 2 +- .../current/security/self-assessment-1.8.md | 2 +- .../current/upgrades/automated.md | 2 +- .../docusaurus-plugin-content-docs/current/upgrades/manual.md | 2 +- .../current/datastore/datastore.md | 2 +- .../current/installation/airgap.md | 2 +- .../current/installation/registry-mirror.md | 2 +- .../current/networking/distributed-multicloud.md | 2 +- .../current/security/hardening-guide.md | 2 +- .../current/security/self-assessment-1.23.md | 2 +- .../current/upgrades/automated.md | 2 +- .../docusaurus-plugin-content-docs/current/upgrades/manual.md | 2 +- .../current/datastore/datastore.md | 2 +- i18n/zh/docusaurus-plugin-content-docs/current/faq.md | 2 +- .../current/installation/airgap.md | 2 +- .../current/installation/network-options.md | 2 +- .../current/installation/registry-mirror.md | 2 +- .../current/networking/distributed-multicloud.md | 2 +- .../current/security/hardening-guide.md | 2 +- .../current/security/self-assessment-1.23.md | 2 +- .../current/upgrades/automated.md | 2 +- .../docusaurus-plugin-content-docs/current/upgrades/manual.md | 2 +- 42 files changed, 42 insertions(+), 42 deletions(-) diff --git a/docs/datastore/datastore.md b/docs/datastore/datastore.md index 438c1023a..bc2b6afa4 100644 --- a/docs/datastore/datastore.md +++ b/docs/datastore/datastore.md @@ -21,7 +21,7 @@ K3s supports the following datastore options: See the [High Availability External DB](ha.md) documentation for more information on using external datastores with multiple servers. The following external datastores are supported: * [etcd](https://etcd.io/) (certified against version 3.5.4) - * [MySQL](https://www.mysql.com/) (certified against versions 5.7 and 8.0) + * [MySQL](https://www.mysql.com) (certified against versions 5.7 and 8.0) * [MariaDB](https://mariadb.org/) (certified against version 10.6.8) * [PostgreSQL](https://www.postgresql.org/) (certified against versions 12.16, 13.12, 14.9 and 15.4) diff --git a/docs/faq.md b/docs/faq.md index d64993b0a..e3c870264 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -52,7 +52,7 @@ For more information on managing K3s join tokens, see the [`k3s token` command d ### How compatible are different versions of K3s? -In general, the [Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/) applies. +In general, the [Kubernetes version skew policy](https://kubernetes.io/releases/version-skew-policy/) applies. In short, servers can be newer than agents, but agents cannot be newer than servers. diff --git a/docs/installation/airgap.md b/docs/installation/airgap.md index c50586a0c..df802e693 100644 --- a/docs/installation/airgap.md +++ b/docs/installation/airgap.md @@ -12,7 +12,7 @@ These steps assume you have already created nodes in your air-gap environment, are using the bundled containerd as the container runtime, and have a OCI-compliant private registry available in your environment. -If you have not yet set up a private Docker registry, refer to the [official Registry documentation](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry). +If you have not yet set up a private Docker registry, refer to the [official Registry documentation](https://distribution.github.io/distribution/about/deploying/#run-an-externally-accessible-registry). #### Create the Registry YAML and Push Images diff --git a/docs/installation/registry-mirror.md b/docs/installation/registry-mirror.md index cb2bfcd1e..e305d6bfa 100644 --- a/docs/installation/registry-mirror.md +++ b/docs/installation/registry-mirror.md @@ -6,7 +6,7 @@ title: "Embedded Registry Mirror" The Embedded Registry Mirror is available as an experimental feature as of January 2024 releases: v1.26.13+k3s1, v1.27.10+k3s1, v1.28.6+k3s1, v1.29.1+k3s1 ::: -K3s embeds [Spegel](https://github.com/XenitAB/spegel), a stateless distributed OCI registry mirror that allows peer-to-peer sharing of container images between nodes in a Kubernetes cluster. +K3s embeds [Spegel](https://github.com/spegel-org/spegel), a stateless distributed OCI registry mirror that allows peer-to-peer sharing of container images between nodes in a Kubernetes cluster. The distributed registry mirror is disabled by default. ## Enabling The Distributed OCI Registry Mirror diff --git a/docs/networking/distributed-multicloud.md b/docs/networking/distributed-multicloud.md index 8e90cf49b..74f936eb7 100644 --- a/docs/networking/distributed-multicloud.md +++ b/docs/networking/distributed-multicloud.md @@ -106,6 +106,6 @@ If you have ACLs activated in Tailscale, you need to add an "accept" rule to all :::warning -If you plan on running several K3s clusters using the same tailscale network, please create appropriate [ACLs](https://tailscale.com/kb/1018/acls/) to avoid IP conflicts or use different podCIDR subnets for each cluster. +If you plan on running several K3s clusters using the same tailscale network, please create appropriate [ACLs](https://tailscale.com/kb/1018/acls) to avoid IP conflicts or use different podCIDR subnets for each cluster. ::: diff --git a/docs/security/hardening-guide.md b/docs/security/hardening-guide.md index 5208d2e63..53ed3acc1 100644 --- a/docs/security/hardening-guide.md +++ b/docs/security/hardening-guide.md @@ -522,7 +522,7 @@ The log directory, ideally, must be created before starting K3s. A restrictive a sudo mkdir -p -m 700 /var/lib/rancher/k3s/server/logs ``` -A starter audit policy to log request metadata is provided below. The policy should be written to a file named `audit.yaml` in `/var/lib/rancher/k3s/server` directory. Detailed information about policy configuration for the API server can be found in the Kubernetes [documentation](https://kubernetes.io/docs/tasks/debug-application-cluster/audit/). +A starter audit policy to log request metadata is provided below. The policy should be written to a file named `audit.yaml` in `/var/lib/rancher/k3s/server` directory. Detailed information about policy configuration for the API server can be found in the Kubernetes [documentation](https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/). ```yaml apiVersion: audit.k8s.io/v1 diff --git a/docs/security/self-assessment-1.23.md b/docs/security/self-assessment-1.23.md index 7cc021ac7..f6b4b9437 100644 --- a/docs/security/self-assessment-1.23.md +++ b/docs/security/self-assessment-1.23.md @@ -8,7 +8,7 @@ This document is a companion to the [K3s security hardening guide](hardening-gui This guide is specific to the **v1.22-v1.23** release lines of K3s and the **v1.23** release of the CIS Kubernetes Benchmark. -For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). +For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes). ### Testing controls methodology diff --git a/docs/security/self-assessment-1.24.md b/docs/security/self-assessment-1.24.md index b9fbe5cf4..267188376 100644 --- a/docs/security/self-assessment-1.24.md +++ b/docs/security/self-assessment-1.24.md @@ -8,7 +8,7 @@ This document is a companion to the [K3s security hardening guide](hardening-gui This guide is specific to the **v1.24** release line of K3s and the **v1.24** release of the CIS Kubernetes Benchmark. -For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). +For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes). ### Testing controls methodology diff --git a/docs/security/self-assessment-1.7.md b/docs/security/self-assessment-1.7.md index 2f5efccfe..ab5d6de25 100644 --- a/docs/security/self-assessment-1.7.md +++ b/docs/security/self-assessment-1.7.md @@ -8,7 +8,7 @@ This document is a companion to the [K3s security hardening guide](hardening-gui This guide is specific to the **v1.25** release line of K3s and the **v1.7.1** release of the CIS Kubernetes Benchmark. -For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.7.1. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). +For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.7.1. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes). ### Testing controls methodology diff --git a/docs/security/self-assessment-1.8.md b/docs/security/self-assessment-1.8.md index 18c593e90..3e6deb096 100644 --- a/docs/security/self-assessment-1.8.md +++ b/docs/security/self-assessment-1.8.md @@ -8,7 +8,7 @@ This document is a companion to the [K3s security hardening guide](hardening-gui This guide is specific to the **v1.26-v1.29** release line of K3s and the **v1.8** release of the CIS Kubernetes Benchmark. -For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.8. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). +For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.8. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes). ### Testing controls methodology diff --git a/docs/upgrades/automated.md b/docs/upgrades/automated.md index 578c311ac..22c0f63a4 100644 --- a/docs/upgrades/automated.md +++ b/docs/upgrades/automated.md @@ -38,7 +38,7 @@ For more details on the design and architecture of the system-upgrade-controller - [k3s-upgrade](https://github.com/k3s-io/k3s-upgrade) :::tip -When attempting to upgrade to a new version of K3s, the [Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version. +When attempting to upgrade to a new version of K3s, the [Kubernetes version skew policy](https://kubernetes.io/releases/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version. ::: ### Install the system-upgrade-controller diff --git a/docs/upgrades/manual.md b/docs/upgrades/manual.md index 3517cd43f..0e803e555 100644 --- a/docs/upgrades/manual.md +++ b/docs/upgrades/manual.md @@ -21,7 +21,7 @@ Upgrades performed via the installation script or using our [automated upgrades] For an exhaustive and up-to-date list of channels, you can visit the [k3s channel service API](https://update.k3s.io/v1-release/channels). For more technical details on how channels work, you see the [channelserver project](https://github.com/rancher/channelserver). :::tip -When attempting to upgrade to a new version of K3s, the [Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version. +When attempting to upgrade to a new version of K3s, the [Kubernetes version skew policy](https://kubernetes.io/releases/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version. ::: ### Upgrade K3s Using the Installation Script diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/datastore/datastore.md b/i18n/ja/docusaurus-plugin-content-docs/current/datastore/datastore.md index 6b209ae5f..f5b9627da 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/datastore/datastore.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/datastore/datastore.md @@ -20,7 +20,7 @@ K3sは以下のデータストアオプションをサポートしています 複数のサーバーで外部データストアを使用する方法については、[高可用性外部DB](ha.md)のドキュメントを参照してください。 以下の外部データストアがサポートされています： * [etcd](https://etcd.io/) (バージョン3.5.4に対して認定) - * [MySQL](https://www.mysql.com/) (バージョン5.7および8.0に対して認定) + * [MySQL](https://www.mysql.com) (バージョン5.7および8.0に対して認定) * [MariaDB](https://mariadb.org/) (バージョン10.6.8に対して認定) * [PostgreSQL](https://www.postgresql.org/) (バージョン12.16、13.12、14.9および15.4に対して認定) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/faq.md b/i18n/ja/docusaurus-plugin-content-docs/current/faq.md index 83deb3e04..bea6653dc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/faq.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/faq.md @@ -50,7 +50,7 @@ K3sの参加トークンの管理に関する詳細は、[`k3s token`コマン ### 異なるバージョンのK3sの互換性はどの程度ですか？ -一般的に、[Kubernetesのバージョンスキューポリシー](https://kubernetes.io/docs/setup/release/version-skew-policy/)が適用されます。 +一般的に、[Kubernetesのバージョンスキューポリシー](https://kubernetes.io/releases/version-skew-policy/)が適用されます。 簡単に言えば、サーバーはエージェントより新しいバージョンであることができますが、エージェントはサーバーより新しいバージョンであってはなりません。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/installation/airgap.md b/i18n/ja/docusaurus-plugin-content-docs/current/installation/airgap.md index 1bd2b1ff4..629fd8d26 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/installation/airgap.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/installation/airgap.md @@ -10,7 +10,7 @@ K3sをエアギャップ環境でインストールするには、2つの方法 これらの手順は、エアギャップ環境でノードを既に作成し、コンテナランタイムとしてバンドルされたcontainerdを使用し、環境内にOCI準拠のプライベートレジストリが利用可能であることを前提としています。 -まだプライベートDockerレジストリを設定していない場合は、[公式レジストリドキュメント](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry)を参照してください。 +まだプライベートDockerレジストリを設定していない場合は、[公式レジストリドキュメント](https://distribution.github.io/distribution/about/deploying/#run-an-externally-accessible-registry)を参照してください。 #### レジストリYAMLの作成とイメージのプッシュ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/installation/registry-mirror.md b/i18n/ja/docusaurus-plugin-content-docs/current/installation/registry-mirror.md index c165f494b..bef33da76 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/installation/registry-mirror.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/installation/registry-mirror.md @@ -6,7 +6,7 @@ title: "埋め込みレジストリミラー" 埋め込みレジストリミラーは、2024年1月のリリースから実験的な機能として利用可能です：v1.26.13+k3s1、v1.27.10+k3s1、v1.28.6+k3s1、v1.29.1+k3s1 ::: -K3sは、Kubernetesクラスター内のノード間でコンテナイメージをピアツーピアで共有できる、ステートレスな分散OCIレジストリミラーである[Spegel](https://github.com/XenitAB/spegel)を埋め込んでいます。 +K3sは、Kubernetesクラスター内のノード間でコンテナイメージをピアツーピアで共有できる、ステートレスな分散OCIレジストリミラーである[Spegel](https://github.com/spegel-org/spegel)を埋め込んでいます。 分散レジストリミラーはデフォルトでは無効になっています。 ## 分散OCIレジストリミラーの有効化 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md b/i18n/ja/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md index be828c434..98b8408c9 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md @@ -78,6 +78,6 @@ Tailscale統合を有効にしてK3sをデプロイするには、各ノード :::warning -同じTailscaleネットワークを使用して複数のK3sクラスターを実行する予定がある場合、IPの競合を避けるために適切な[ACL](https://tailscale.com/kb/1018/acls/)を作成するか、各クラスターに異なるpodCIDRサブネットを使用してください。 +同じTailscaleネットワークを使用して複数のK3sクラスターを実行する予定がある場合、IPの競合を避けるために適切な[ACL](https://tailscale.com/kb/1018/acls)を作成するか、各クラスターに異なるpodCIDRサブネットを使用してください。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/security/hardening-guide.md b/i18n/ja/docusaurus-plugin-content-docs/current/security/hardening-guide.md index 1efe6e939..c793f5793 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/security/hardening-guide.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/security/hardening-guide.md @@ -520,7 +520,7 @@ CIS 要件 1.2.22 から 1.2.25 は、API サーバーの監査ログの設定 sudo mkdir -p -m 700 /var/lib/rancher/k3s/server/logs ``` -リクエストメタデータをログに記録するための初期監査ポリシーを以下に示します。このポリシーは `/var/lib/rancher/k3s/server` ディレクトリに `audit.yaml` という名前のファイルに書き込む必要があります。API サーバーのポリシー設定に関する詳細情報は、Kubernetes の[ドキュメント](https://kubernetes.io/docs/tasks/debug-application-cluster/audit/)に記載されています。 +リクエストメタデータをログに記録するための初期監査ポリシーを以下に示します。このポリシーは `/var/lib/rancher/k3s/server` ディレクトリに `audit.yaml` という名前のファイルに書き込む必要があります。API サーバーのポリシー設定に関する詳細情報は、Kubernetes の[ドキュメント](https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/)に記載されています。 ```yaml apiVersion: audit.k8s.io/v1 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md b/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md index 5db047477..7631bc53f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md @@ -9,7 +9,7 @@ title: CIS 1.23 自己評価ガイド このガイドはK3sの**v1.22-v1.23**リリースラインおよびCIS Kubernetesベンチマークの**v1.23**リリースに特化しています。 -各コントロールに関する詳細な説明やテスト失敗時の修正方法については、CIS Kubernetesベンチマークv1.6の該当セクションを参照してください。ベンチマークは[Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/)で無料アカウントを作成後にダウンロードできます。 +各コントロールに関する詳細な説明やテスト失敗時の修正方法については、CIS Kubernetesベンチマークv1.6の該当セクションを参照してください。ベンチマークは[Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes)で無料アカウントを作成後にダウンロードできます。 ### コントロールテストの方法論 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.24.md b/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.24.md index 35df582c0..47abb8545 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.24.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.24.md @@ -8,7 +8,7 @@ title: CIS 1.24 自己評価ガイド このガイドはK3sの**v1.24**リリースラインおよびCIS Kubernetesベンチマークの**v1.24**リリースに特化しています。 -各コントロールの詳細な説明やテスト失敗時の修正方法については、CIS Kubernetesベンチマークv1.6の該当セクションを参照してください。ベンチマークは、無料アカウントを作成後に[Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/)からダウンロードできます。 +各コントロールの詳細な説明やテスト失敗時の修正方法については、CIS Kubernetesベンチマークv1.6の該当セクションを参照してください。ベンチマークは、無料アカウントを作成後に[Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes)からダウンロードできます。 ### コントロールテストの方法論 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.7.md b/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.7.md index d81b58aa0..640974d03 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.7.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.7.md @@ -8,7 +8,7 @@ title: CIS 1.7 セルフアセスメントガイド このガイドは K3s の **v1.25-v1.26** リリースラインおよび CIS Kubernetes ベンチマークの **v1.7.1** リリースに特化しています。 -各コントロールに関する詳細な説明やテスト失敗時の修正方法については、CIS Kubernetes ベンチマーク v1.7.1 の該当セクションを参照してください。ベンチマークは、無料アカウントを作成した後に [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/) からダウンロードできます。 +各コントロールに関する詳細な説明やテスト失敗時の修正方法については、CIS Kubernetes ベンチマーク v1.7.1 の該当セクションを参照してください。ベンチマークは、無料アカウントを作成した後に [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes) からダウンロードできます。 ### コントロールテストの方法論 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.8.md b/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.8.md index 8d58667e4..0cce3fe1c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.8.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/security/self-assessment-1.8.md @@ -8,7 +8,7 @@ title: CIS 1.8 セルフアセスメントガイド このガイドはK3sの**v1.27-v1.29**リリースラインおよびCIS Kubernetesベンチマークの**v1.8**リリースに特化しています。 -各コントロールの詳細な説明やテスト失敗時の修正方法については、CIS Kubernetesベンチマークv1.8の該当セクションを参照してください。ベンチマークは、無料アカウントを作成後に[Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/)からダウンロードできます。 +各コントロールの詳細な説明やテスト失敗時の修正方法については、CIS Kubernetesベンチマークv1.8の該当セクションを参照してください。ベンチマークは、無料アカウントを作成後に[Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes)からダウンロードできます。 ### コントロールテストの方法論 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/upgrades/automated.md b/i18n/ja/docusaurus-plugin-content-docs/current/upgrades/automated.md index 3feb4d758..e5412c6e7 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/upgrades/automated.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/upgrades/automated.md @@ -37,7 +37,7 @@ system-upgrade-controllerの設計とアーキテクチャ、またはK3sとの - [k3s-upgrade](https://github.com/k3s-io/k3s-upgrade) :::tip -K3sの新しいバージョンにアップグレードする際には、[Kubernetesバージョンスキューポリシー](https://kubernetes.io/docs/setup/release/version-skew-policy/)が適用されます。アップグレード時に中間のマイナーバージョンをスキップしないようにプランを設定してください。system-upgrade-controller自体は、Kubernetesバージョンのサポートされていない変更を防ぎません。 +K3sの新しいバージョンにアップグレードする際には、[Kubernetesバージョンスキューポリシー](https://kubernetes.io/releases/version-skew-policy/)が適用されます。アップグレード時に中間のマイナーバージョンをスキップしないようにプランを設定してください。system-upgrade-controller自体は、Kubernetesバージョンのサポートされていない変更を防ぎません。 ::: ### system-upgrade-controllerのインストール diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/upgrades/manual.md b/i18n/ja/docusaurus-plugin-content-docs/current/upgrades/manual.md index 8c30f59bb..263ef088b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/upgrades/manual.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/upgrades/manual.md @@ -21,7 +21,7 @@ K3sをアップグレードするには、インストールスクリプトを チャンネルの包括的かつ最新のリストについては、[k3sチャンネルサービスAPI](https://update.k3s.io/v1-release/channels)を参照してください。チャンネルの動作に関する技術的な詳細については、[channelserverプロジェクト](https://github.com/rancher/channelserver)を参照してください。 :::tip -K3sの新しいバージョンにアップグレードする際には、[Kubernetesバージョンスキューポリシー](https://kubernetes.io/docs/setup/release/version-skew-policy/)が適用されます。アップグレード時に中間のマイナーバージョンをスキップしないように計画を立ててください。system-upgrade-controller自体は、Kubernetesバージョンのサポートされていない変更を防ぐことはありません。 +K3sの新しいバージョンにアップグレードする際には、[Kubernetesバージョンスキューポリシー](https://kubernetes.io/releases/version-skew-policy/)が適用されます。アップグレード時に中間のマイナーバージョンをスキップしないように計画を立ててください。system-upgrade-controller自体は、Kubernetesバージョンのサポートされていない変更を防ぐことはありません。 ::: ### インストールスクリプトを使用してK3sをアップグレードする diff --git a/i18n/kr/docusaurus-plugin-content-docs/current/datastore/datastore.md b/i18n/kr/docusaurus-plugin-content-docs/current/datastore/datastore.md index 33573e7a8..93bffd706 100644 --- a/i18n/kr/docusaurus-plugin-content-docs/current/datastore/datastore.md +++ b/i18n/kr/docusaurus-plugin-content-docs/current/datastore/datastore.md @@ -21,7 +21,7 @@ K3s는 다음과 같은 데이터스토어 옵션을 지원합니다: 여러 서버에서 외부 데이터스토어를 사용하는 방법에 대한 자세한 내용은 [고가용성 외부 DB](ha.md) 설명서를 참조하세요. 지원되는 외부 데이터스토어는 다음과 같습니다: - [etcd](https://etcd.io/) (3.5.4 버전에 대해 검증됨) - - [MySQL](https://www.mysql.com/) (5.7 and 8.0 버전에 대해 검증됨) + - [MySQL](https://www.mysql.com) (5.7 and 8.0 버전에 대해 검증됨) - [MariaDB](https://mariadb.org/) (10.6.8 버전에 대해 검증됨) - [PostgreSQL](https://www.postgresql.org/) (10.7, 11.5, and 14.2 버전에 대해 검증됨) diff --git a/i18n/kr/docusaurus-plugin-content-docs/current/installation/airgap.md b/i18n/kr/docusaurus-plugin-content-docs/current/installation/airgap.md index 383cd326c..0a13bb1ef 100644 --- a/i18n/kr/docusaurus-plugin-content-docs/current/installation/airgap.md +++ b/i18n/kr/docusaurus-plugin-content-docs/current/installation/airgap.md @@ -12,7 +12,7 @@ These steps assume you have already created nodes in your air-gap environment, are using the bundled containerd as the container runtime, and have a OCI-compliant private registry available in your environment. -If you have not yet set up a private Docker registry, refer to the [official Registry documentation](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry). +If you have not yet set up a private Docker registry, refer to the [official Registry documentation](https://distribution.github.io/distribution/about/deploying/#run-an-externally-accessible-registry). #### Create the Registry YAML and Push Images diff --git a/i18n/kr/docusaurus-plugin-content-docs/current/installation/registry-mirror.md b/i18n/kr/docusaurus-plugin-content-docs/current/installation/registry-mirror.md index 82b74e675..3a1c6ab60 100644 --- a/i18n/kr/docusaurus-plugin-content-docs/current/installation/registry-mirror.md +++ b/i18n/kr/docusaurus-plugin-content-docs/current/installation/registry-mirror.md @@ -6,7 +6,7 @@ title: "Embedded Registry Mirror" The Embedded Registry Mirror is available as an experimental feature as of January 2024 releases: v1.26.13+k3s1, v1.27.10+k3s1, v1.28.6+k3s1, v1.29.1+k3s1 ::: -K3s embeds [Spegel](https://github.com/XenitAB/spegel), a stateless distributed OCI registry mirror that allows peer-to-peer sharing of container images between nodes in a Kubernetes cluster. +K3s embeds [Spegel](https://github.com/spegel-org/spegel), a stateless distributed OCI registry mirror that allows peer-to-peer sharing of container images between nodes in a Kubernetes cluster. The distributed registry mirror is disabled by default. ## Enabling The Distributed OCI Registry Mirror diff --git a/i18n/kr/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md b/i18n/kr/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md index 62efa1790..111aeaff7 100644 --- a/i18n/kr/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md +++ b/i18n/kr/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md @@ -78,6 +78,6 @@ Optionally, if you have your own Tailscale server (e.g. headscale), you can conn :::warning -If you plan on running several K3s clusters using the same tailscale network, please create appropriate [ACLs](https://tailscale.com/kb/1018/acls/) to avoid IP conflicts or use different podCIDR subnets for each cluster. +If you plan on running several K3s clusters using the same tailscale network, please create appropriate [ACLs](https://tailscale.com/kb/1018/acls) to avoid IP conflicts or use different podCIDR subnets for each cluster. ::: diff --git a/i18n/kr/docusaurus-plugin-content-docs/current/security/hardening-guide.md b/i18n/kr/docusaurus-plugin-content-docs/current/security/hardening-guide.md index 394b9ada2..e608abc32 100644 --- a/i18n/kr/docusaurus-plugin-content-docs/current/security/hardening-guide.md +++ b/i18n/kr/docusaurus-plugin-content-docs/current/security/hardening-guide.md @@ -524,7 +524,7 @@ The log directory, ideally, must be created before starting K3s. A restrictive a sudo mkdir -p -m 700 /var/lib/rancher/k3s/server/logs ``` -A starter audit policy to log request metadata is provided below. The policy should be written to a file named `audit.yaml` in `/var/lib/rancher/k3s/server` directory. Detailed information about policy configuration for the API server can be found in the Kubernetes [documentation](https://kubernetes.io/docs/tasks/debug-application-cluster/audit/). +A starter audit policy to log request metadata is provided below. The policy should be written to a file named `audit.yaml` in `/var/lib/rancher/k3s/server` directory. Detailed information about policy configuration for the API server can be found in the Kubernetes [documentation](https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/). ```yaml apiVersion: audit.k8s.io/v1 diff --git a/i18n/kr/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md b/i18n/kr/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md index 8e4a5321b..df2c5cf8d 100644 --- a/i18n/kr/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md +++ b/i18n/kr/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md @@ -10,7 +10,7 @@ This document is a companion to the [K3s security hardening guide](hardening-gui This guide is specific to the **v1.22**, **v1.23** and **v1.24** release line of K3s and the **v1.23** release of the CIS Kubernetes Benchmark. -For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). +For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes). #### Testing controls methodology diff --git a/i18n/kr/docusaurus-plugin-content-docs/current/upgrades/automated.md b/i18n/kr/docusaurus-plugin-content-docs/current/upgrades/automated.md index 257790075..941e28e39 100644 --- a/i18n/kr/docusaurus-plugin-content-docs/current/upgrades/automated.md +++ b/i18n/kr/docusaurus-plugin-content-docs/current/upgrades/automated.md @@ -36,7 +36,7 @@ For more details on the design and architecture of the system-upgrade-controller - [k3s-upgrade](https://github.com/k3s-io/k3s-upgrade) :::tip -When attempting to upgrade to a new version of K3s, the [Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version. +When attempting to upgrade to a new version of K3s, the [Kubernetes version skew policy](https://kubernetes.io/releases/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version. ::: ### Install the system-upgrade-controller diff --git a/i18n/kr/docusaurus-plugin-content-docs/current/upgrades/manual.md b/i18n/kr/docusaurus-plugin-content-docs/current/upgrades/manual.md index 5466b361a..0182042cb 100644 --- a/i18n/kr/docusaurus-plugin-content-docs/current/upgrades/manual.md +++ b/i18n/kr/docusaurus-plugin-content-docs/current/upgrades/manual.md @@ -21,7 +21,7 @@ Upgrades performed via the installation script or using our [automated upgrades] For an exhaustive and up-to-date list of channels, you can visit the [k3s channel service API](https://update.k3s.io/v1-release/channels). For more technical details on how channels work, you see the [channelserver project](https://github.com/rancher/channelserver). :::tip -When attempting to upgrade to a new version of K3s, the [Kubernetes version skew policy](https://kubernetes.io/docs/setup/release/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version. +When attempting to upgrade to a new version of K3s, the [Kubernetes version skew policy](https://kubernetes.io/releases/version-skew-policy/) applies. Ensure that your plan does not skip intermediate minor versions when upgrading. The system-upgrade-controller itself will not protect against unsupported changes to the Kubernetes version. ::: ### Upgrade K3s Using the Installation Script diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/datastore/datastore.md b/i18n/zh/docusaurus-plugin-content-docs/current/datastore/datastore.md index d5816370f..2e1678d32 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/datastore/datastore.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/datastore/datastore.md @@ -21,7 +21,7 @@ K3s 支持以下数据存储选项： 有关在具有多个 Server 的情况下使用外部数据存储，请参阅[高可用外部数据库](ha.md)文档。 支持以下外部数据存储： * [etcd](https://etcd.io/)（针对版本 3.5.4 进行了认证） - * [MySQL](https://www.mysql.com/)（针对版本 5.7 和 8.0 进行了认证） + * [MySQL](https://www.mysql.com)（针对版本 5.7 和 8.0 进行了认证） * [MariaDB](https://mariadb.org/)（针对版本 10.6.8 进行了认证） * [PostgreSQL](https://www.postgresql.org/)（针对版本 10.7、11.5 和 14.2 进行了认证） diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/faq.md b/i18n/zh/docusaurus-plugin-content-docs/current/faq.md index a9328c249..e88bddaf4 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/faq.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/faq.md @@ -48,7 +48,7 @@ Kubernetes 使用名为 `klog` 的日志管理框架，该框架对进程中的 ### 不同版本的 K3s 兼容性如何？ -通常，[Kubernetes 版本倾斜策略](https://kubernetes.io/docs/setup/release/version-skew-policy/)适用。 +通常，[Kubernetes 版本倾斜策略](https://kubernetes.io/releases/version-skew-policy/)适用。 简而言之，Server 版本可以比 Agnet 新，但 Agent 不能比 Server 新。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/installation/airgap.md b/i18n/zh/docusaurus-plugin-content-docs/current/installation/airgap.md index 383cd326c..0a13bb1ef 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/installation/airgap.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/installation/airgap.md @@ -12,7 +12,7 @@ These steps assume you have already created nodes in your air-gap environment, are using the bundled containerd as the container runtime, and have a OCI-compliant private registry available in your environment. -If you have not yet set up a private Docker registry, refer to the [official Registry documentation](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry). +If you have not yet set up a private Docker registry, refer to the [official Registry documentation](https://distribution.github.io/distribution/about/deploying/#run-an-externally-accessible-registry). #### Create the Registry YAML and Push Images diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/installation/network-options.md b/i18n/zh/docusaurus-plugin-content-docs/current/installation/network-options.md index b9fd9675f..d60c886c0 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/installation/network-options.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/installation/network-options.md @@ -261,6 +261,6 @@ Optionally, if you have your own Tailscale server (e.g. headscale), you can conn :::warning -If you plan on running several K3s clusters using the same tailscale network, please create appropriate [ACLs](https://tailscale.com/kb/1018/acls/) to avoid IP conflicts or use different podCIDR subnets for each cluster. +If you plan on running several K3s clusters using the same tailscale network, please create appropriate [ACLs](https://tailscale.com/kb/1018/acls) to avoid IP conflicts or use different podCIDR subnets for each cluster. ::: diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/installation/registry-mirror.md b/i18n/zh/docusaurus-plugin-content-docs/current/installation/registry-mirror.md index 82b74e675..3a1c6ab60 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/installation/registry-mirror.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/installation/registry-mirror.md @@ -6,7 +6,7 @@ title: "Embedded Registry Mirror" The Embedded Registry Mirror is available as an experimental feature as of January 2024 releases: v1.26.13+k3s1, v1.27.10+k3s1, v1.28.6+k3s1, v1.29.1+k3s1 ::: -K3s embeds [Spegel](https://github.com/XenitAB/spegel), a stateless distributed OCI registry mirror that allows peer-to-peer sharing of container images between nodes in a Kubernetes cluster. +K3s embeds [Spegel](https://github.com/spegel-org/spegel), a stateless distributed OCI registry mirror that allows peer-to-peer sharing of container images between nodes in a Kubernetes cluster. The distributed registry mirror is disabled by default. ## Enabling The Distributed OCI Registry Mirror diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md b/i18n/zh/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md index 62efa1790..111aeaff7 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/networking/distributed-multicloud.md @@ -78,6 +78,6 @@ Optionally, if you have your own Tailscale server (e.g. headscale), you can conn :::warning -If you plan on running several K3s clusters using the same tailscale network, please create appropriate [ACLs](https://tailscale.com/kb/1018/acls/) to avoid IP conflicts or use different podCIDR subnets for each cluster. +If you plan on running several K3s clusters using the same tailscale network, please create appropriate [ACLs](https://tailscale.com/kb/1018/acls) to avoid IP conflicts or use different podCIDR subnets for each cluster. ::: diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/security/hardening-guide.md b/i18n/zh/docusaurus-plugin-content-docs/current/security/hardening-guide.md index 5e264efb4..68987be7f 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/security/hardening-guide.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/security/hardening-guide.md @@ -527,7 +527,7 @@ The log directory, ideally, must be created before starting K3s. A restrictive a sudo mkdir -p -m 700 /var/lib/rancher/k3s/server/logs ``` -A starter audit policy to log request metadata is provided below. The policy should be written to a file named `audit.yaml` in `/var/lib/rancher/k3s/server` directory. Detailed information about policy configuration for the API server can be found in the Kubernetes [documentation](https://kubernetes.io/docs/tasks/debug-application-cluster/audit/). +A starter audit policy to log request metadata is provided below. The policy should be written to a file named `audit.yaml` in `/var/lib/rancher/k3s/server` directory. Detailed information about policy configuration for the API server can be found in the Kubernetes [documentation](https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/). ```yaml apiVersion: audit.k8s.io/v1 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md b/i18n/zh/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md index 3a1fdfadd..5860e65ad 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/security/self-assessment-1.23.md @@ -14,7 +14,7 @@ This document is a companion to the [K3s security hardening guide](hardening-gui This guide is specific to the **v1.22**, **v1.23** and **v1.24** release line of K3s and the **v1.23** release of the CIS Kubernetes Benchmark. -For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes/). +For more information about each control, including detailed descriptions and remediations for failing tests, you can refer to the corresponding section of the CIS Kubernetes Benchmark v1.6. You can download the benchmark, after creating a free account, in [Center for Internet Security (CIS)](https://www.cisecurity.org/benchmark/kubernetes). #### Testing controls methodology diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/upgrades/automated.md b/i18n/zh/docusaurus-plugin-content-docs/current/upgrades/automated.md index 259165d55..db6da13d7 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/upgrades/automated.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/upgrades/automated.md @@ -38,7 +38,7 @@ title: "自动升级" - [k3s-upgrade](https://github.com/k3s-io/k3s-upgrade) :::tip -尝试升级到 K3s 新版本时，[Kubernetes 版本倾斜策略](https://kubernetes.io/docs/setup/release/version-skew-policy/)适用。确保你的计划在升级时不会跳过中间次要版本。system-upgrade-controller 本身不会防止更改到不支持的 Kubernetes 版本。 +尝试升级到 K3s 新版本时，[Kubernetes 版本倾斜策略](https://kubernetes.io/releases/version-skew-policy/)适用。确保你的计划在升级时不会跳过中间次要版本。system-upgrade-controller 本身不会防止更改到不支持的 Kubernetes 版本。 ::: ### 安装 system-upgrade-controller diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/upgrades/manual.md b/i18n/zh/docusaurus-plugin-content-docs/current/upgrades/manual.md index 92ac0eccb..3326248d3 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/upgrades/manual.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/upgrades/manual.md @@ -21,7 +21,7 @@ title: "手动升级" 有关详细的最新 channel 列表，你可以访问 [k3s channel 服务 API](https://update.k3s.io/v1-release/channels)。有关 channel 如何工作的更多信息，请参阅 [channelserver 项目](https://github.com/rancher/channelserver)。 :::tip -尝试升级到 K3s 新版本时，[Kubernetes 版本倾斜策略](https://kubernetes.io/docs/setup/release/version-skew-policy/)适用。确保你的计划在升级时不会跳过中间次要版本。system-upgrade-controller 本身不会防止更改到不支持的 Kubernetes 版本。 +尝试升级到 K3s 新版本时，[Kubernetes 版本倾斜策略](https://kubernetes.io/releases/version-skew-policy/)适用。确保你的计划在升级时不会跳过中间次要版本。system-upgrade-controller 本身不会防止更改到不支持的 Kubernetes 版本。 ::: ### 使用安装脚本升级 K3s