From 20f3c5fd4c9db60e683837218d88758b09f0cdea Mon Sep 17 00:00:00 2001 From: Lucas Saintarbor Date: Wed, 6 Aug 2025 11:52:55 -0700 Subject: [PATCH 1/4] Remove RKE1: /integrations-in-rancher pages Part 1 (#1946) * Remove RKE reference in logging-helm-chart-options * Remove RKE reference in neuvector/overview * Remove RKE reference in monitoring-and-alerting/how-monitoring-works --- .../logging/logging-helm-chart-options.md | 1 - .../how-monitoring-works.md | 23 +++--- .../neuvector/overview.md | 80 ++++++------------- .../logging/logging-helm-chart-options.md | 1 - .../how-monitoring-works.md | 22 ++--- .../neuvector/overview.md | 1 - .../logging/logging-helm-chart-options.md | 1 - .../how-monitoring-works.md | 22 ++--- .../neuvector/overview.md | 1 - .../logging/logging-helm-chart-options.md | 1 - .../how-monitoring-works.md | 23 +++--- .../neuvector/overview.md | 15 ++-- 12 files changed, 77 insertions(+), 114 deletions(-) diff --git a/docs/integrations-in-rancher/logging/logging-helm-chart-options.md b/docs/integrations-in-rancher/logging/logging-helm-chart-options.md index 2c1a79e4132..1c77d299816 100644 --- a/docs/integrations-in-rancher/logging/logging-helm-chart-options.md +++ b/docs/integrations-in-rancher/logging/logging-helm-chart-options.md @@ -59,7 +59,6 @@ The following table summarizes the sources where additional logs may be collecte | Logging Source | Linux Nodes (including in Windows cluster) | Windows Nodes | | --- | --- | ---| -| RKE | ✓ | ✓ | | RKE2 | ✓ | | | K3s | ✓ | | | AKS | ✓ | | diff --git a/docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 514c1828af9..1a34415ea58 100644 --- a/docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -216,8 +216,7 @@ The following Kubernetes components are directly scraped by Prometheus: \* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. -** For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. - +** For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. ### Scraping Metrics Based on Kubernetes Distribution @@ -225,18 +224,18 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w
How Metrics are Exposed to Prometheus
-| Kubernetes Component | RKE | RKE2 | KubeADM | K3s | +| Kubernetes Component | RKE2 | KubeADM | K3s | |-----|-----|-----|-----|-----| -| kube-controller-manager | rkeControllerManager.enabled |rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | -| kube-scheduler | rkeScheduler.enabled | rke2Scheduler.enabled |kubeAdmScheduler.enabled | k3sServer.enabled | -| etcd | rkeEtcd.enabled | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | -| kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | -| kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | -| ingress-nginx* | Collects metrics directly exposed by kubelet, exposed by rkeIngressNginx.enabled | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | -| coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | -| kube-api-server | Collects metrics directly exposed by kube-api-server |Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | +| kube-controller-manager | rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | +| kube-scheduler | rke2Scheduler.enabled |kubeAdmScheduler.enabled | k3sServer.enabled | +| etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | +| kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | +| kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | +| ingress-nginx* | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | +| coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | +| kube-api-server | Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | -\* For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +\* For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. ### Terminology diff --git a/docs/integrations-in-rancher/neuvector/overview.md b/docs/integrations-in-rancher/neuvector/overview.md index cf7ec91cdd9..968e45d820b 100644 --- a/docs/integrations-in-rancher/neuvector/overview.md +++ b/docs/integrations-in-rancher/neuvector/overview.md @@ -23,17 +23,16 @@ The Harvester Helm Chart is used to manage access to the NeuVector UI in Rancher Some examples are as follows: - - RKE1: `docker` - - K3s and RKE2: `k3scontainerd` - - AKS: `containerd` for v1.19 and up - - EKS: `docker` for v1.22 and below; `containerd` for v1.23 and up - - GKE: `containerd` (see the [Google docs](https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd) for more) +- K3s and RKE2: `k3scontainerd` +- AKS: `containerd` for v1.19 and up +- EKS: `docker` for v1.22 and below; `containerd` for v1.23 and up +- GKE: `containerd` (see the [Google docs](https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd) for more) - :::note + :::note - Only one container runtime engine may be selected at a time during installation. + Only one container runtime engine may be selected at a time during installation. - ::: + ::: **To navigate to and install the NeuVector chart through Cluster Tools:** @@ -102,63 +101,36 @@ Below are the minimum recommended computing resources for the NeuVector chart in \* Minimum 1GB of memory total required for Controller, Manager, and Scanner containers combined. - ## Hardened Cluster Support - Calico and Canal - - +NeuVector components Controller and Enforcer are deployable if PSP is set to true. - - All NeuVector components are deployable if PSP is set to true. +**Applicable to NeuVector chart version 100.0.0+up2.2.0 only:** - You will need to set additional configuration for your hardened cluster environment as follows: +For Manager, Scanner, and Updater components, additional configuration is required as shown below: - 1. Click **☰ > Cluster Management**. - 1. Go to the cluster that you created and click **Explore**. - 1. In the left navigation bar, click **Apps**. - 1. Install (or upgrade to) NeuVector version `100.0.1+up2.2.2`. +```sh +kubectl patch deploy neuvector-manager-pod -n cattle-neuvector-system --patch '{"spec":{"template":{"spec":{"securityContext":{"runAsUser": 5400}}}}}' +kubectl patch deploy neuvector-scanner-pod -n cattle-neuvector-system --patch '{"spec":{"template":{"spec":{"securityContext":{"runAsUser": 5400}}}}}' +kubectl patch cronjob neuvector-updater-pod -n cattle-neuvector-system --patch '{"spec":{"jobTemplate":{"spec":{"template":{"spec":{"securityContext":{"runAsUser": 5400}}}}}}}' +``` - - Under **Edit Options** > **Other Configuration**, enable **Pod Security Policy** by checking the box (no other config needed): +You will need to set additional configuration for your hardened cluster environment. - ![Enable PSP for RKE1 Hardened Cluster](/img/psp-nv-rke.png) +:::note +You must update your config in both RKE2 and K3s hardened clusters as shown below. +::: - 1. Click **Install** at the bottom-right to complete. +1. Click **☰ > Cluster Management**. +1. Go to the cluster that you created and click **Explore**. +1. In the left navigation bar, click **Apps**. +1. Install (or upgrade to) NeuVector version `100.0.1+up2.2.2`. +- Under **Edit Options** > **Other Configuration**, enable **Pod Security Policy** by checking the box. Note that you must also enter a value greater than `zero` for `Manager runAsUser ID`, `Scanner runAsUser ID`, and `Updater runAsUser ID`: - - - - - NeuVector components Controller and Enforcer are deployable if PSP is set to true. - - - **Applicable to NeuVector chart version 100.0.0+up2.2.0 only:** - - - For Manager, Scanner, and Updater components, additional configuration is required as shown below: - - ``` - kubectl patch deploy neuvector-manager-pod -n cattle-neuvector-system --patch '{"spec":{"template":{"spec":{"securityContext":{"runAsUser": 5400}}}}}' - kubectl patch deploy neuvector-scanner-pod -n cattle-neuvector-system --patch '{"spec":{"template":{"spec":{"securityContext":{"runAsUser": 5400}}}}}' - kubectl patch cronjob neuvector-updater-pod -n cattle-neuvector-system --patch '{"spec":{"jobTemplate":{"spec":{"template":{"spec":{"securityContext":{"runAsUser": 5400}}}}}}}' - ``` -
- - You will need to set additional configuration for your hardened cluster environment. - - >**Note:** You must update your config in both RKE2 and K3s hardened clusters as shown below. - - 1. Click **☰ > Cluster Management**. - 1. Go to the cluster that you created and click **Explore**. - 1. In the left navigation bar, click **Apps**. - 1. Install (or upgrade to) NeuVector version `100.0.1+up2.2.2`. - - - Under **Edit Options** > **Other Configuration**, enable **Pod Security Policy** by checking the box. Note that you must also enter a value greater than `zero` for `Manager runAsUser ID`, `Scanner runAsUser ID`, and `Updater runAsUser ID`: - - ![Enable PSP for RKE2 and K3s Hardened Clusters](/img/psp-nv-rke2.png) - - 1. Click **Install** at the bottom-right to complete. - - - + ![Enable PSP for RKE2 and K3s Hardened Clusters](/img/psp-nv-rke2.png) +1. Click **Install** at the bottom-right to complete. ## SELinux-enabled Cluster Support - Calico and Canal diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging-helm-chart-options.md b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging-helm-chart-options.md index 40bae8aa4de..a6b72b66af6 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging-helm-chart-options.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging-helm-chart-options.md @@ -55,7 +55,6 @@ Logging v2 已在 RHEL/CentOS 7 和 8 上使用 SELinux 进行了测试。 | 日志来源 | Linux 节点（包括在 Windows 集群中） | Windows 节点 | | --- | --- | ---| -| RKE | ✓ | ✓ | | RKE2 | ✓ | | | K3s | ✓ | | | AKS | ✓ | | diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 2dbd49f42d2..fb4a5c764c4 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -211,7 +211,7 @@ Prometheus 直接抓取以下 Kubernetes 组件： \* 你可以选择通过 `hardenedKubelet.enabled` 来使用 PushProx，但这不是默认设置。 -\*\* RKE 和 RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\*\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 ### 基于 Kubernetes 发行版抓取指标 @@ -220,18 +220,18 @@ Prometheus 直接抓取以下 Kubernetes 组件：
指标如何暴露给 Prometheus
-| Kubernetes 组件 | RKE | RKE2 | KubeADM | K3s | +| Kubernetes 组件 | RKE2 | KubeADM | K3s | |-----|-----|-----|-----|-----| -| kube-controller-manager | rkeControllerManager.enabled | rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | -| kube-scheduler | rkeScheduler.enabled | rke2Scheduler.enabled | kubeAdmScheduler.enabled | k3sServer.enabled | -| etcd | rkeEtcd.enabled | rke2Etcd.enabled | kubeAdmEtcd.enabled | 不可用 | -| kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | -| kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | -| ingress-nginx* | 收集 kubelet 直接公开的指标，由 rkeIngressNginx.enabled 公开 | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | -| coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | -| kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | +| kube-controller-manager | rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | +| kube-scheduler | rke2Scheduler.enabled | kubeAdmScheduler.enabled | k3sServer.enabled | +| etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | 不可用 | +| kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | +| kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | +| ingress-nginx* | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | +| coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | +| kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | -\* RKE 和 RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 ### 名词解释 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/neuvector/overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/neuvector/overview.md index 79bb6f1760c..f28cd25e3bd 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/neuvector/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/neuvector/overview.md @@ -25,7 +25,6 @@ Harvester Helm Chart 用于管理 Rancher 中 NeuVector UI 的访问，用户可 以下是一些例子： -- RKE1：`docker` - K3s 和 RKE2：`k3scontainerd` - AKS：`containerd` 适用于 v1.19 及更高版本 - EKS：`docker` 适用于 v1.22 及以下版本；`containerd` 适用于 v1.23 及更高版本 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/logging/logging-helm-chart-options.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/logging/logging-helm-chart-options.md index 40bae8aa4de..a6b72b66af6 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/logging/logging-helm-chart-options.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/logging/logging-helm-chart-options.md @@ -55,7 +55,6 @@ Logging v2 已在 RHEL/CentOS 7 和 8 上使用 SELinux 进行了测试。 | 日志来源 | Linux 节点（包括在 Windows 集群中） | Windows 节点 | | --- | --- | ---| -| RKE | ✓ | ✓ | | RKE2 | ✓ | | | K3s | ✓ | | | AKS | ✓ | | diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 2dbd49f42d2..fb4a5c764c4 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -211,7 +211,7 @@ Prometheus 直接抓取以下 Kubernetes 组件： \* 你可以选择通过 `hardenedKubelet.enabled` 来使用 PushProx，但这不是默认设置。 -\*\* RKE 和 RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\*\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 ### 基于 Kubernetes 发行版抓取指标 @@ -220,18 +220,18 @@ Prometheus 直接抓取以下 Kubernetes 组件：
指标如何暴露给 Prometheus
-| Kubernetes 组件 | RKE | RKE2 | KubeADM | K3s | +| Kubernetes 组件 | RKE2 | KubeADM | K3s | |-----|-----|-----|-----|-----| -| kube-controller-manager | rkeControllerManager.enabled | rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | -| kube-scheduler | rkeScheduler.enabled | rke2Scheduler.enabled | kubeAdmScheduler.enabled | k3sServer.enabled | -| etcd | rkeEtcd.enabled | rke2Etcd.enabled | kubeAdmEtcd.enabled | 不可用 | -| kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | -| kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | -| ingress-nginx* | 收集 kubelet 直接公开的指标，由 rkeIngressNginx.enabled 公开 | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | -| coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | -| kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | +| kube-controller-manager | rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | +| kube-scheduler | rke2Scheduler.enabled | kubeAdmScheduler.enabled | k3sServer.enabled | +| etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | 不可用 | +| kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | +| kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | +| ingress-nginx* | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | +| coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | +| kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | -\* RKE 和 RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 ### 名词解释 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/neuvector/overview.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/neuvector/overview.md index 79bb6f1760c..f28cd25e3bd 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/neuvector/overview.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/neuvector/overview.md @@ -25,7 +25,6 @@ Harvester Helm Chart 用于管理 Rancher 中 NeuVector UI 的访问，用户可 以下是一些例子： -- RKE1：`docker` - K3s 和 RKE2：`k3scontainerd` - AKS：`containerd` 适用于 v1.19 及更高版本 - EKS：`docker` 适用于 v1.22 及以下版本；`containerd` 适用于 v1.23 及更高版本 diff --git a/versioned_docs/version-2.12/integrations-in-rancher/logging/logging-helm-chart-options.md b/versioned_docs/version-2.12/integrations-in-rancher/logging/logging-helm-chart-options.md index 2c1a79e4132..1c77d299816 100644 --- a/versioned_docs/version-2.12/integrations-in-rancher/logging/logging-helm-chart-options.md +++ b/versioned_docs/version-2.12/integrations-in-rancher/logging/logging-helm-chart-options.md @@ -59,7 +59,6 @@ The following table summarizes the sources where additional logs may be collecte | Logging Source | Linux Nodes (including in Windows cluster) | Windows Nodes | | --- | --- | ---| -| RKE | ✓ | ✓ | | RKE2 | ✓ | | | K3s | ✓ | | | AKS | ✓ | | diff --git a/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 514c1828af9..1a34415ea58 100644 --- a/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -216,8 +216,7 @@ The following Kubernetes components are directly scraped by Prometheus: \* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. -** For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. - +** For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. ### Scraping Metrics Based on Kubernetes Distribution @@ -225,18 +224,18 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w
How Metrics are Exposed to Prometheus
-| Kubernetes Component | RKE | RKE2 | KubeADM | K3s | +| Kubernetes Component | RKE2 | KubeADM | K3s | |-----|-----|-----|-----|-----| -| kube-controller-manager | rkeControllerManager.enabled |rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | -| kube-scheduler | rkeScheduler.enabled | rke2Scheduler.enabled |kubeAdmScheduler.enabled | k3sServer.enabled | -| etcd | rkeEtcd.enabled | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | -| kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | -| kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | -| ingress-nginx* | Collects metrics directly exposed by kubelet, exposed by rkeIngressNginx.enabled | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | -| coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | -| kube-api-server | Collects metrics directly exposed by kube-api-server |Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | +| kube-controller-manager | rke2ControllerManager.enabled | kubeAdmControllerManager.enabled | k3sServer.enabled | +| kube-scheduler | rke2Scheduler.enabled |kubeAdmScheduler.enabled | k3sServer.enabled | +| etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | +| kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | +| kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | +| ingress-nginx* | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | +| coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | +| kube-api-server | Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | -\* For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +\* For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. ### Terminology diff --git a/versioned_docs/version-2.12/integrations-in-rancher/neuvector/overview.md b/versioned_docs/version-2.12/integrations-in-rancher/neuvector/overview.md index cf7ec91cdd9..0c081570cbf 100644 --- a/versioned_docs/version-2.12/integrations-in-rancher/neuvector/overview.md +++ b/versioned_docs/version-2.12/integrations-in-rancher/neuvector/overview.md @@ -23,17 +23,16 @@ The Harvester Helm Chart is used to manage access to the NeuVector UI in Rancher Some examples are as follows: - - RKE1: `docker` - - K3s and RKE2: `k3scontainerd` - - AKS: `containerd` for v1.19 and up - - EKS: `docker` for v1.22 and below; `containerd` for v1.23 and up - - GKE: `containerd` (see the [Google docs](https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd) for more) +- K3s and RKE2: `k3scontainerd` +- AKS: `containerd` for v1.19 and up +- EKS: `docker` for v1.22 and below; `containerd` for v1.23 and up +- GKE: `containerd` (see the [Google docs](https://cloud.google.com/kubernetes-engine/docs/concepts/using-containerd) for more) - :::note + :::note - Only one container runtime engine may be selected at a time during installation. + Only one container runtime engine may be selected at a time during installation. - ::: + ::: **To navigate to and install the NeuVector chart through Cluster Tools:** From 7f398140471e39478090d68e2c57e0de3f19c1bf Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Thu, 7 Aug 2025 15:55:01 -0700 Subject: [PATCH 2/4] [2.12] Add missing flag to enable auditlog --- .../installation-references/helm-chart-options.md | 2 +- .../installation-references/helm-chart-options.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md b/docs/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md index c37ff478ad1..3ee46920bbd 100644 --- a/docs/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md +++ b/docs/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md @@ -81,7 +81,7 @@ Enabling the [API Audit Log](../../../how-to-guides/advanced-user-guides/enable- You can collect this log as you would any container log. Enable [logging](../../../integrations-in-rancher/logging/logging.md) for the `System` Project on the Rancher server cluster. ```plain ---set auditLog.level=1 +--set auditLog.enabled=true --set auditLog.level=1 ``` By default enabling Audit Logging will create a sidecar container in the Rancher pod. This container (`rancher-audit-log`) will stream the log to `stdout`. You can collect this log as you would any container log. When using the sidecar as the audit log destination, the `hostPath`, `maxAge`, `maxBackups`, and `maxSize` options do not apply. It's advised to use your OS or Docker daemon's log rotation features to control disk space use. Enable [logging](../../../integrations-in-rancher/logging/logging.md) for the Rancher server cluster or System Project. diff --git a/versioned_docs/version-2.12/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md b/versioned_docs/version-2.12/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md index c37ff478ad1..3ee46920bbd 100644 --- a/versioned_docs/version-2.12/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md +++ b/versioned_docs/version-2.12/getting-started/installation-and-upgrade/installation-references/helm-chart-options.md @@ -81,7 +81,7 @@ Enabling the [API Audit Log](../../../how-to-guides/advanced-user-guides/enable- You can collect this log as you would any container log. Enable [logging](../../../integrations-in-rancher/logging/logging.md) for the `System` Project on the Rancher server cluster. ```plain ---set auditLog.level=1 +--set auditLog.enabled=true --set auditLog.level=1 ``` By default enabling Audit Logging will create a sidecar container in the Rancher pod. This container (`rancher-audit-log`) will stream the log to `stdout`. You can collect this log as you would any container log. When using the sidecar as the audit log destination, the `hostPath`, `maxAge`, `maxBackups`, and `maxSize` options do not apply. It's advised to use your OS or Docker daemon's log rotation features to control disk space use. Enable [logging](../../../integrations-in-rancher/logging/logging.md) for the Rancher server cluster or System Project. From 94ff32cc805119d140f78848db04dec7e3e3b204 Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Fri, 8 Aug 2025 14:31:29 -0700 Subject: [PATCH 3/4] Remove invalid node and cluster drivers --- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 63 ----------- .../huawei.md | 104 ------------------ ...usters-from-hosted-kubernetes-providers.md | 6 - .../tencent.md | 103 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 59 ---------- .../huawei.md | 100 ----------------- ...usters-from-hosted-kubernetes-providers.md | 6 - .../tencent.md | 99 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 59 ---------- .../huawei.md | 100 ----------------- ...usters-from-hosted-kubernetes-providers.md | 7 +- .../tencent.md | 99 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 59 ---------- .../huawei.md | 100 ----------------- ...usters-from-hosted-kubernetes-providers.md | 7 +- .../tencent.md | 99 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 59 ---------- .../huawei.md | 100 ----------------- ...usters-from-hosted-kubernetes-providers.md | 6 - .../tencent.md | 99 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 59 ---------- .../huawei.md | 100 ----------------- ...usters-from-hosted-kubernetes-providers.md | 7 +- .../tencent.md | 99 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 59 ---------- .../huawei.md | 100 ----------------- ...usters-from-hosted-kubernetes-providers.md | 7 +- .../tencent.md | 99 ----------------- .../about-provisioning-drivers.md | 6 - ...usters-from-hosted-kubernetes-providers.md | 6 - sidebars.js | 3 - .../about-provisioning-drivers.md | 6 - .../alibaba.md | 63 ----------- .../huawei.md | 104 ------------------ ...usters-from-hosted-kubernetes-providers.md | 6 - .../tencent.md | 103 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 63 ----------- .../huawei.md | 104 ------------------ ...usters-from-hosted-kubernetes-providers.md | 6 - .../tencent.md | 103 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 63 ----------- .../huawei.md | 104 ------------------ ...usters-from-hosted-kubernetes-providers.md | 6 - .../tencent.md | 103 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 63 ----------- .../huawei.md | 104 ------------------ ...usters-from-hosted-kubernetes-providers.md | 6 - .../tencent.md | 103 ----------------- .../about-provisioning-drivers.md | 6 - .../alibaba.md | 63 ----------- .../huawei.md | 104 ------------------ ...usters-from-hosted-kubernetes-providers.md | 6 - .../tencent.md | 103 ----------------- versioned_sidebars/version-2.10-sidebars.json | 5 +- versioned_sidebars/version-2.11-sidebars.json | 5 +- versioned_sidebars/version-2.12-sidebars.json | 5 +- versioned_sidebars/version-2.8-sidebars.json | 5 +- versioned_sidebars/version-2.9-sidebars.json | 5 +- 68 files changed, 9 insertions(+), 3347 deletions(-) delete mode 100644 docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md delete mode 100644 versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md delete mode 100644 versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md delete mode 100644 versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index 63b78e20f4c..6edd8965a06 100644 --- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ By default, Rancher has activated several hosted Kubernetes cloud providers incl * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -There are several other hosted Kubernetes cloud providers that are disabled by default, but are packaged in Rancher: - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ### Node Drivers Node drivers are used to provision hosts, which Rancher uses to launch and manage Kubernetes clusters. A node driver is the same as a [Docker Machine driver](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. diff --git a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index 82cdde8861f..00000000000 --- a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Creating an Aliyun ACK Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Alibaba Cloud Kubernetes (ACK). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for ACK, but by default, this cluster driver is `inactive`. In order to launch ACK clusters, you will need to [enable the ACK cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning ACK clusters. - -## Prerequisites Outside of Rancher - -:::caution - -Deploying to ACK will incur charges. - -::: - -1. In Aliyun, activate the following services in their respective consoles. - - - [Container Service](https://cs.console.aliyun.com) - - [Resource Orchestration Service](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. Make sure that the account you will be using to create the ACK cluster has the appropriate permissions. Referring to the official Alibaba Cloud documentation about [Role authorization](https://www.alibabacloud.com/help/doc-detail/86483.htm) and [Use the Container Service console as a RAM user](https://www.alibabacloud.com/help/doc-detail/86484.htm) for details. - -3. In Alibaba Cloud, create an [access key](https://www.alibabacloud.com/help/doc-detail/53045.html). - -4. In Alibaba Cloud, create an [SSH key pair](https://www.alibabacloud.com/help/doc-detail/51793.html). This key is used to access nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Alibaba ACK cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Alibaba ACK** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Alibaba ACK clusters in Rancher. - -## Create an ACK Cluster - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, click **Create**. -1. Choose **Alibaba ACK**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Configure **Account Access** for the ACK cluster. Choose the geographical region in which to build your cluster, and input the access key that was created as part of the prerequisite steps. -1. Click **Next: Configure Cluster**, then choose cluster type, the version of Kubernetes and the availability zone. -1. If you choose **Kubernetes** as the cluster type, Click **Next: Configure Master Nodes**, then complete the **Master Nodes** form. -1. Click **Next: Configure Worker Nodes**, then complete the **Worker Nodes** form. -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index cbde0642b88..00000000000 --- a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -title: Creating a Huawei CCE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Huawei Cloud Container Engine (CCE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for CCE, but by default, this cluster driver is `inactive`. In order to launch CCE clusters, you will need to [enable the CCE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning CCE clusters. - -## Prerequisites in Huawei - -:::caution - -Deploying to CCE will incur charges. - -::: - -1. Find your project ID in Huawei CCE portal. See the CCE documentation on how to [manage your projects](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214). - -2. Create an [Access Key ID and Secret Access Key](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html). - -## Prerequisite in Rancher - -You will need to enable the Huawei CCE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Huawei CCE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Huawei CCE clusters in Rancher. - -## Limitations - -Huawei CCE service doesn't support the ability to create clusters with public access through their API. You are required to run Rancher in the same VPC as the CCE clusters that you want to provision. - -## Create the CCE Cluster - -1. From the **Clusters** page, click **Create**. -1. Click **Huawei CCE**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Enter **Project Id**, Access Key ID as **Access Key** and Secret Access Key **Secret Key**. Then Click **Next: Configure cluster**. Fill in the cluster configuration. For help filling out the form, refer to [Huawei CCE Configuration.](#huawei-cce-configuration) -1. Fill the following node configuration of the cluster. For help filling out the form, refer to [Node Configuration.](#node-configuration) -1. Click **Create** to create the CCE cluster. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -## Huawei CCE Configuration - -|Settings|Description| -|---|---| -| Cluster Type | Which type or node you want to include into the cluster, `VirtualMachine` or `BareMetal`. | -| Description | The description of the cluster. | -| Master Version | The Kubernetes version. | -| Management Scale Count | The max node count of the cluster. The options are 50, 200 and 1000. The larger of the scale count, the more the cost. | -| High Availability | Enable master node high availability. The cluster with high availability enabled will have more cost. | -| Container Network Mode | The network mode used in the cluster. `overlay_l2` and `vpc-router` is supported in `VirtualMachine` type and `underlay_ipvlan` is supported in `BareMetal` type | -| Container Network CIDR | Network CIDR for the cluster. | -| VPC Name | The VPC name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| Subnet Name | The Subnet name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| External Server | This option is reserved for the future we can enable CCE cluster public access via API. For now, it is always disabled. | -| Cluster Label | The labels for the cluster. | -| Highway Subnet | This option is only supported in `BareMetal` type. It requires you to select a VPC with high network speed for the bare metal machines. | - -:::note - -If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - -::: - -## Node Configuration - -|Settings|Description| -|---|---| -| Zone | The available zone at where the node(s) of the cluster is deployed. | -| Billing Mode | The bill mode for the cluster node(s). In `VirtualMachine` type, only `Pay-per-use` is supported. in `BareMetal`, you can choose `Pay-per-use` or `Yearly/Monthly`. | -| Validity Period | This option only shows in `Yearly/Monthly` bill mode. It means how long you want to pay for the cluster node(s). | -| Auto Renew | This option only shows in `Yearly/Monthly` bill mode. It means that the cluster node(s) will renew the `Yearly/Monthly` payment automatically or not. | -| Data Volume Type | Data volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Data Volume Size | Data volume size for the cluster node(s) | -| Root Volume Type | Root volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Root Volume Size | Root volume size for the cluster node(s) | -| Node Flavor | The node flavor of the cluster node(s). The flavor list in Rancher UI is fetched from Huawei Cloud. It includes all the supported node flavors. | -| Node Count | The node count of the cluster | -| Node Operating System | The operating system for the cluster node(s). Only `EulerOS 2.2` and `CentOS 7.4` are supported right now. | -| SSH Key Name | The ssh key for the cluster node(s) | -| EIP | The public IP options for the cluster node(s). `Disabled` means that the cluster node(s) are not going to bind a public IP. `Create EIP` means that the cluster node(s) will bind one or many newly created Eips after provisioned and more options will be shown in the UI to set the to-create EIP parameters. And `Select Existed EIP` means that the node(s) will bind to the EIPs you select. | -| EIP Count | This option will only be shown when `Create EIP` is selected. It means how many EIPs you want to create for the node(s). | -| EIP Type | This option will only be shown when `Create EIP` is selected. The options are `5_bgp` and `5_sbgp`. | -| EIP Share Type | This option will only be shown when `Create EIP` is selected. The only option is `PER`. | -| EIP Charge Mode | This option will only be shown when `Create EIP` is selected. The options are pay by `BandWidth` and pay by `Traffic`. | -| EIP Bandwidth Size | This option will only be shown when `Create EIP` is selected. The BandWidth of the EIPs. | -| Authentication Mode | It means enabling `RBAC` or also enabling `Authenticating Proxy`. If you select `Authenticating Proxy`, the certificate which is used for authenticating proxy will be also required. | -| Node Label | The labels for the cluster node(s). Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) | \ No newline at end of file diff --git a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index ea0cc4ff394..946906ae614 100644 --- a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher supports the following Kubernetes providers: - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## Hosted Kubernetes Provider Authentication @@ -28,6 +25,3 @@ When using Rancher to create a cluster hosted by a provider, you are prompted fo - [Creating a GKE Cluster](gke.md) - [Creating an EKS Cluster](eks.md) - [Creating an AKS Cluster](aks.md) -- [Creating an ACK Cluster](alibaba.md) -- [Creating a TKE Cluster](tencent.md) -- [Creating a CCE Cluster](huawei.md) diff --git a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 35cd4cc9b1c..00000000000 --- a/docs/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Creating a Tencent TKE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Tencent Kubernetes Engine (TKE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for TKE, but by default, this cluster driver is `inactive`. In order to launch TKE clusters, you will need to [enable the TKE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning TKE clusters. - -## Prerequisites in Tencent - -:::caution - -Deploying to TKE will incur charges. - -::: - -1. Make sure that the account you will be using to create the TKE cluster has the appropriate permissions by referring to the [Cloud Access Management](https://intl.cloud.tencent.com/document/product/598/10600) documentation for details. - -2. Create a [Cloud API Secret ID and Secret Key](https://console.cloud.tencent.com/capi). - -3. Create a [Private Network and Subnet](https://intl.cloud.tencent.com/document/product/215/4927) in the region that you want to deploy your Kubernetes cluster. - -4. Create a [SSH key pair](https://intl.cloud.tencent.com/document/product/213/6092). This key is used to access the nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Tencent TKE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Tencent TKE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Tencent TKE clusters in Rancher. - -## Create a TKE Cluster - -1. From the **Clusters** page, click **Create**. - -2. Choose **Tencent TKE**. - -3. Enter a **Cluster Name**. - -4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. - -5. Configure **Account Access** for the TKE cluster. Complete each drop-down and field using the information obtained in [Prerequisites](#prerequisites-in-tencent). - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Region | From the drop-down chooses the geographical region in which to build your cluster. | - | Secret ID | Enter the Secret ID that you obtained from the Tencent Cloud Console. | - | Secret Key | Enter the Secret key that you obtained from Tencent Cloud Console. | - -6. Click `Next: Configure Cluster` to set your TKE cluster configurations. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes Version | The TKE only supports Kubernetes version 1.10.5 now. | - | Node Count | Enter the amount of worker node you want to purchase for your Kubernetes cluster, up to 100. | - | VPC | Select the VPC name that you have created in the Tencent Cloud Console. | - | Container Network CIDR | Enter the CIDR range of your Kubernetes cluster, you may check the available range of the CIDR in the VPC service of the Tencent Cloud Console. Default to 172.16.0.0/16. | - - :::note - - If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that, cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure in Rancher v2.3.0+.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - - ::: - -7. Click `Next: Select Instance Type` to choose the instance type that will use for your TKE cluster. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Availability Zone | Choose the availability zone of the VPC region. | - | Subnet | Select the Subnet that you have created within the VPC, and add a new one if you don't have it in the chosen availability zone. | - | Instance Type | From the drop-down chooses the VM instance type that you want to use for the TKE cluster, default to S2.MEDIUM4 (CPU 2 Memory 4 GiB). | - -8. Click `Next: Configure Instance` to configure the VM instance that will use for your TKE cluster. - - Option | Description - -------|------------ - Operating System | The name of the operating system, currently supports Centos7.2x86_64 or ubuntu16.04.1 LTSx86_64 - Security Group | Security group ID, default does not bind any security groups. - Root Disk Type | System disk type. System disk type restrictions are detailed in the [CVM instance configuration](https://cloud.tencent.com/document/product/213/11518). - Root Disk Size | System disk size. Linux system adjustment range is 20 - 50G, step size is 1. - Data Disk Type | Data disk type, default value to the SSD cloud drive - Data Disk Size | Data disk size (GB), the step size is 10 - Band Width Type | Type of bandwidth, PayByTraffic or PayByHour - Band Width | Public network bandwidth (Mbps) - Key Pair | Key id, after associating the key can be used to logging to the VM node - -9. Click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index c10c4b83785..efcd02f34ba 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ Rancher 中有两种类型的驱动： * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -还有几个托管的 Kubernetes 云提供商是默认禁用的，但也打包在 Rancher 中： - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ## 主机驱动 主机驱动用于配置主机，Rancher 使用这些主机启动和管理 Kubernetes 集群。主机驱动与 [Docker Machine 驱动](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md)相同。创建主机模板时可以显示的主机驱动，是由主机驱动的状态定义的。只有 `active` 主机驱动将显示为创建节点模板的选项。默认情况下，Rancher 与许多现有的 Docker Machine 驱动打包在一起，但你也可以创建自定义主机驱动并添加到 Rancher。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index a10200d37fa..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: 创建阿里云 ACK 集群 ---- - -你可以使用 Rancher 创建托管在阿里云 Alibaba Cloud Kubernetes (ACK) 中的集群。Rancher 已经为 ACK 实现并打包了针对 ACK 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 ACK 集群，你需要[启用 ACK 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 ACK 集群。 - -## Rancher 之外的先决条件 - -:::caution - -部署到 ACK 会产生费用。 - -::: - -1. 在阿里云中，在对应的控制台中激活以下服务。 - - - [容器服务](https://cs.console.aliyun.com) - - [资源编排服务](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. 确保你用于创建 ACK 集群的账号具有适当的权限。详见阿里云[角色授权](https://www.alibabacloud.com/help/doc-detail/86483.htm)和[使用容器服务控制台作为 RAM 用户](https://www.alibabacloud.com/help/doc-detail/86484.htm)官方文档。 - -3. 在阿里云中，创建[访问密钥](https://www.alibabacloud.com/help/doc-detail/53045.html)。 - -4. 在阿里云中，创建 [SSH 密钥对](https://www.alibabacloud.com/help/doc-detail/51793.html)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用阿里云 ACK 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Alibaba ACK** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建阿里云 ACK 集群了。 - -## 创建 ACK 集群 - -1. 点击 **☰ > 集群管理**。 -1. 在**集群**页面，点击**创建**。 -1. 单击 **Alibaba ACK**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 为 ACK 集群配置**账号访问**。选择要在其中构建集群的地理区域，并输入在先决条件步骤中创建的访问密钥。 -1. 点击**下一步：配置集群**，然后选择集群类型、Kubernetes 版本和可用区。 -1. 如果选择 **Kubernetes** 作为集群类型，请单击**下一步：配置 master 节点**，然后填写 **master 节点**表单。 -1. 单击**下一步：配置 Worker 节点**，然后填写 **Worker 节点**表单。 -1. 检查并确认你的选项。然后单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index b6244c617d6..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: 创建华为 CCE 集群 ---- - -你可以使用 Rancher 创建托管在华为云容器引擎 (CCE) 中的集群。Rancher 已经为 CCE 实现并打包了针对 CCE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 CCE 集群，你需要[启用 CCE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 CCE 集群。 - -## 华为先决条件 - -:::caution - -部署到 CCE 会产生费用。 - -::: - -1. 在华为 CCE 门户中找到你的项目 ID。请参阅 CCE 文档以了解如何[管理你的项目](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214)。 - -2. 创建一个[访问密钥 ID 和密文访问密钥](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html)。 - -## Rancher 先决条件 - -你需要启用华为 CCE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Huawei CCE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建华为 CCE 集群了。 - -## 限制 - -华为 CCE 服务不支持通过其 API 创建具有公共访问权限的集群。你需要在要配置的 CCE 集群的相同 VPC 中运行 Rancher。 - -## 创建 CCE 集群 - -1. 在**集群**页面，点击**创建**。 -1. 单击 **Huawei CCE**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 输入**项目 ID**，访问密钥 ID，**Access Key**，和密文访问密钥 **Secret Key**。然后点击**下一步：配置集群**。填写集群配置。有关填写表单的帮助，请参阅[华为 CCE 配置](#华为-cce-配置)。 -1. 填写集群的以下节点配置。有关填写表单的帮助，请参阅[节点配置](#节点配置)。 -1. 点击**创建**来创建 CCE 集群。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 - -## 华为 CCE 配置 - -| 设置 | 描述 | -|---|---| -| 集群类型 | 要包含到集群的节点类型，可以是 `VirtualMachine` 或 `BareMetal`。 | -| 描述 | 集群的描述。 | -| 主版本 | Kubernetes 版本。 | -| 管理规模数量 | 集群的最大节点数。选项为 50、200 和 1000。规模计数越大，成本越高。 | -| 高可用性 | 启用 master 节点的高可用性。启用高可用性的集群成本会更高。 | -| 容器网络模式 | 集群中使用的网络模式。`VirtualMachine` 支持 `overlay_l2` 和 `vpc-router`，而 `BareMetal` 支持 `underlay_ipvlan`。 | -| 容器网络 CIDR | 集群的网络 CIDR。 | -| VPC 名称 | 要部署集群的 VPC 名称。如果留空，Rancher 将创建一个。 | -| 子网名称 | 要部署集群的子网名称。如果留空，Rancher 将创建一个。 | -| 外部服务器 | 预留选项，用于通过 API 启用 CCE 集群的公共访问。这个选项暂时是一直禁用的。 | -| 集群标签 | 集群的标签。 | -| 高速子网 | 只有 `BareMetal` 支持该选项。裸机要求选择网速高的 VPC。 | - -:::note - -如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅[配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - -::: - -## 节点配置 - -| 设置 | 描述 | -|---|---| -| 地区 | 部署集群节点的可用区域。 | -| 计费方式 | 集群节点的计费模式。`VirtualMachine` 仅支持 `Pay-per-use`。`BareMetal` 支持 `Pay-per-use` 或 `Yearly/Monthly`。 | -| 有效期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示支付集群节点费用的时间。 | -| 自动续期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示是否为集群节点自动续期 `Yearly/Monthly` 计费。 | -| 数据卷类型 | 集群节点的数据卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 数据量大小 | 集群节点的数据卷大小。 | -| 根卷类型 | 集群节点的根卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 根卷大小 | 集群节点的根卷大小。 | -| 节点风格 | 集群节点的节点风格。Rancher UI 中的风格列表取自华为云。其中包括所有支持的节点风格。 | -| 节点数 | 集群的节点数 | -| 节点操作系统 | 集群节点的操作系统。目前仅支持 `EulerOS 2.2` 和 `CentOS 7.4`。 | -| SSH 密钥名称 | 集群节点的 SSH 密钥 | -| EIP | 集群节点的公共 IP 选项。`已禁用`表示集群节点不会绑定公共 IP。`创建 EIP`表示集群节点在配置后将绑定一个或多个新创建的 EIP，UI 中将显示更多用来创建 EIP 参数的选项。`选择现有 EIP` 表示节点将绑定到你选择的 EIP。 | -| EIP 数量 | 此选项仅在选择`创建 EIP`时显示。表示你要为节点创建的 EIP 数量。 | -| EIP 类型 | 此选项仅在选择`创建 EIP`时显示。可选 `5_bgp` 和 `5_sbgp`。 | -| EIP 共享类型 | 此选项仅在选择`创建 EIP`时显示。仅可选 `PER`。 | -| EIP 收费模式 | 此选项仅在选择`创建 EIP`时显示。选择按照`带宽`或`流量`计费。 | -| EIP 带宽大小 | 此选项仅在选择`创建 EIP`时显示。EIP 的带宽。 | -| 身份验证模式 | 表示启用 `RBAC`，或同时启用`认证代理`。如果选择`认证代理`，则还需要用于验证代理的证书。 | -| 节点标签 | 集群节点的标签。无效标签会阻止升级，或阻止 Rancher 启动。有关标签语法的详细信息，请参阅 [Kubernetes 文档](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)。 | \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index dd034e3daf8..b034f3df70a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher 支持以下 Kubernetes 提供商： - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## 托管 Kubernetes 提供商的认证 @@ -28,6 +25,3 @@ Rancher 支持以下 Kubernetes 提供商： - [创建 GKE 集群](gke.md) - [创建 EKS 集群](eks.md) - [创建 AKS 集群](aks.md) -- [创建 ACK 集群](alibaba.md) -- [创建 TKE 集群](tencent.md) -- [创建 CCE 集群](huawei.md) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 13349de2c08..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: 创建腾讯 TKE 集群 ---- - -你可以使用 Rancher 创建托管在腾讯 Tencent Kubernetes Engine (TKE) 中的集群。Rancher 已经为 TKE 实现并打包了针对 TKE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 TKE 集群，你需要[启用 TKE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 TKE 集群。 - -## 腾讯先决条件 - -:::caution - -部署到 TKE 会产生费用。 - -::: - -1. 参见[云访问管理](https://intl.cloud.tencent.com/document/product/598/10600)文档，确保用于创建 TKE 集群的账号具有适当的权限。 - -2. 创建[云 API 密钥 ID 和密钥](https://console.cloud.tencent.com/capi)。 - -3. 在要部署 Kubernetes 集群的区域中创建[私有网络和子网](https://intl.cloud.tencent.com/document/product/215/4927)。 - -4. 创建 [SSH 密钥对](https://intl.cloud.tencent.com/document/product/213/6092)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用腾讯 TKE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Tencent TKE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建腾讯 TKE 集群了。 - -## 创建 TKE 集群 - -1. 在**集群**页面，点击**创建**。 - -2. 选择 **Tencent TKE**。 - -3. 输入**集群名称**。 - -4. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 - -5. 为 TKE 集群配置**账号访问**。使用[先决条件](#腾讯先决条件)中获得的信息完成每个下拉列表和字段。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 区域 | 从下拉列表中选择构建集群的地理区域。 | - | 密文 ID | 输入从腾讯云控制台获取的密文 ID。 | - | 密文密钥 | 输入从腾讯云控制台获取的密文密钥。 | - -6. 然后，单击`下一步：配置集群`来配置 TKE 集群。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes 版本 | TKE 目前只支持 Kubernetes 1.10.5。 | - | 节点数 | 输入要为 Kubernetes 集群购买的 worker 节点数，最大值是 100。 | - | VPC | 选择在腾讯云控制台中创建的 VPC 名称。 | - | 容器网络 CIDR | 输入 Kubernetes 集群的 CIDR 范围。你可以在腾讯云控制台的 VPC 服务中查看该 CIDR 的可用范围。默认为 172.16.0.0/16。 | - - :::note - - 如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅 [Rancher 2.3.0+ 配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - - ::: - -7. 点击`下一步：选择实例类型`，然后选择将用于 TKE 集群的实例类型。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 可用区 | 选择 VPC 区域的可用区。 | - | 子网 | 选择你在 VPC 中创建的子网。如果在所选可用区中没有该子网，请添加一个新子网。 | - | 实例类型 | 从下拉列表中选择要用于 TKE 集群的 VM 实例类型，默认为 S2.MEDIUM4（CPU 2；内存 4 GiB）。 | - -8. 点击`下一步：配置实例`，配置用于 TKE 集群的 VM 实例。 - - | 选项 | 描述 | - -------|------------ - | 操作系统 | 操作系统名称，目前支持 Centos7.2x86_64 或 ubuntu16.04.1 LTSx86_64。 | - | 安全组 | 安全组 ID，默认不绑定任何安全组。 | - | 根磁盘类型 | 系统盘类型。系统盘类型限制详见 [CVM 实例配置](https://cloud.tencent.com/document/product/213/11518)。 | - | 根磁盘大小 | 系统盘大小。Linux 系统调整范围为 20-50 GB，步长为 1。 | - | 数据盘类型 | 数据盘类型，默认为 SSD 云盘。 | - | 数据磁盘大小 | 数据盘大小（GB），步长为 10。 | - | 带宽类型 | 带宽收费类型，PayByTraffic 或 PayByHour。 | - | 带宽 | 公网带宽 (Mbps) | - | 密钥对 | 密钥 ID，关联后可以用来登录 VM 节点。 | - -9. 单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index cb1637d2bc8..e45f9e486c7 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ Rancher 中有两种类型的驱动： * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -还有几个托管的 Kubernetes 云提供商是默认禁用的，但也打包在 Rancher 中： - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ## 主机驱动 主机驱动用于配置主机，Rancher 使用这些主机启动和管理 Kubernetes 集群。主机驱动与 [Docker Machine 驱动](https://docs.docker.com/machine/drivers/)相同。创建主机模板时可以显示的主机驱动，是由主机驱动的状态定义的。只有 `active` 主机驱动将显示为创建节点模板的选项。默认情况下，Rancher 与许多现有的 Docker Machine 驱动打包在一起，但你也可以创建自定义主机驱动并添加到 Rancher。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index a10200d37fa..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: 创建阿里云 ACK 集群 ---- - -你可以使用 Rancher 创建托管在阿里云 Alibaba Cloud Kubernetes (ACK) 中的集群。Rancher 已经为 ACK 实现并打包了针对 ACK 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 ACK 集群，你需要[启用 ACK 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 ACK 集群。 - -## Rancher 之外的先决条件 - -:::caution - -部署到 ACK 会产生费用。 - -::: - -1. 在阿里云中，在对应的控制台中激活以下服务。 - - - [容器服务](https://cs.console.aliyun.com) - - [资源编排服务](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. 确保你用于创建 ACK 集群的账号具有适当的权限。详见阿里云[角色授权](https://www.alibabacloud.com/help/doc-detail/86483.htm)和[使用容器服务控制台作为 RAM 用户](https://www.alibabacloud.com/help/doc-detail/86484.htm)官方文档。 - -3. 在阿里云中，创建[访问密钥](https://www.alibabacloud.com/help/doc-detail/53045.html)。 - -4. 在阿里云中，创建 [SSH 密钥对](https://www.alibabacloud.com/help/doc-detail/51793.html)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用阿里云 ACK 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Alibaba ACK** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建阿里云 ACK 集群了。 - -## 创建 ACK 集群 - -1. 点击 **☰ > 集群管理**。 -1. 在**集群**页面，点击**创建**。 -1. 单击 **Alibaba ACK**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 为 ACK 集群配置**账号访问**。选择要在其中构建集群的地理区域，并输入在先决条件步骤中创建的访问密钥。 -1. 点击**下一步：配置集群**，然后选择集群类型、Kubernetes 版本和可用区。 -1. 如果选择 **Kubernetes** 作为集群类型，请单击**下一步：配置 master 节点**，然后填写 **master 节点**表单。 -1. 单击**下一步：配置 Worker 节点**，然后填写 **Worker 节点**表单。 -1. 检查并确认你的选项。然后单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index b6244c617d6..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: 创建华为 CCE 集群 ---- - -你可以使用 Rancher 创建托管在华为云容器引擎 (CCE) 中的集群。Rancher 已经为 CCE 实现并打包了针对 CCE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 CCE 集群，你需要[启用 CCE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 CCE 集群。 - -## 华为先决条件 - -:::caution - -部署到 CCE 会产生费用。 - -::: - -1. 在华为 CCE 门户中找到你的项目 ID。请参阅 CCE 文档以了解如何[管理你的项目](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214)。 - -2. 创建一个[访问密钥 ID 和密文访问密钥](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html)。 - -## Rancher 先决条件 - -你需要启用华为 CCE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Huawei CCE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建华为 CCE 集群了。 - -## 限制 - -华为 CCE 服务不支持通过其 API 创建具有公共访问权限的集群。你需要在要配置的 CCE 集群的相同 VPC 中运行 Rancher。 - -## 创建 CCE 集群 - -1. 在**集群**页面，点击**创建**。 -1. 单击 **Huawei CCE**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 输入**项目 ID**，访问密钥 ID，**Access Key**，和密文访问密钥 **Secret Key**。然后点击**下一步：配置集群**。填写集群配置。有关填写表单的帮助，请参阅[华为 CCE 配置](#华为-cce-配置)。 -1. 填写集群的以下节点配置。有关填写表单的帮助，请参阅[节点配置](#节点配置)。 -1. 点击**创建**来创建 CCE 集群。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 - -## 华为 CCE 配置 - -| 设置 | 描述 | -|---|---| -| 集群类型 | 要包含到集群的节点类型，可以是 `VirtualMachine` 或 `BareMetal`。 | -| 描述 | 集群的描述。 | -| 主版本 | Kubernetes 版本。 | -| 管理规模数量 | 集群的最大节点数。选项为 50、200 和 1000。规模计数越大，成本越高。 | -| 高可用性 | 启用 master 节点的高可用性。启用高可用性的集群成本会更高。 | -| 容器网络模式 | 集群中使用的网络模式。`VirtualMachine` 支持 `overlay_l2` 和 `vpc-router`，而 `BareMetal` 支持 `underlay_ipvlan`。 | -| 容器网络 CIDR | 集群的网络 CIDR。 | -| VPC 名称 | 要部署集群的 VPC 名称。如果留空，Rancher 将创建一个。 | -| 子网名称 | 要部署集群的子网名称。如果留空，Rancher 将创建一个。 | -| 外部服务器 | 预留选项，用于通过 API 启用 CCE 集群的公共访问。这个选项暂时是一直禁用的。 | -| 集群标签 | 集群的标签。 | -| 高速子网 | 只有 `BareMetal` 支持该选项。裸机要求选择网速高的 VPC。 | - -:::note - -如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅[配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - -::: - -## 节点配置 - -| 设置 | 描述 | -|---|---| -| 地区 | 部署集群节点的可用区域。 | -| 计费方式 | 集群节点的计费模式。`VirtualMachine` 仅支持 `Pay-per-use`。`BareMetal` 支持 `Pay-per-use` 或 `Yearly/Monthly`。 | -| 有效期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示支付集群节点费用的时间。 | -| 自动续期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示是否为集群节点自动续期 `Yearly/Monthly` 计费。 | -| 数据卷类型 | 集群节点的数据卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 数据量大小 | 集群节点的数据卷大小。 | -| 根卷类型 | 集群节点的根卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 根卷大小 | 集群节点的根卷大小。 | -| 节点风格 | 集群节点的节点风格。Rancher UI 中的风格列表取自华为云。其中包括所有支持的节点风格。 | -| 节点数 | 集群的节点数 | -| 节点操作系统 | 集群节点的操作系统。目前仅支持 `EulerOS 2.2` 和 `CentOS 7.4`。 | -| SSH 密钥名称 | 集群节点的 SSH 密钥 | -| EIP | 集群节点的公共 IP 选项。`已禁用`表示集群节点不会绑定公共 IP。`创建 EIP`表示集群节点在配置后将绑定一个或多个新创建的 EIP，UI 中将显示更多用来创建 EIP 参数的选项。`选择现有 EIP` 表示节点将绑定到你选择的 EIP。 | -| EIP 数量 | 此选项仅在选择`创建 EIP`时显示。表示你要为节点创建的 EIP 数量。 | -| EIP 类型 | 此选项仅在选择`创建 EIP`时显示。可选 `5_bgp` 和 `5_sbgp`。 | -| EIP 共享类型 | 此选项仅在选择`创建 EIP`时显示。仅可选 `PER`。 | -| EIP 收费模式 | 此选项仅在选择`创建 EIP`时显示。选择按照`带宽`或`流量`计费。 | -| EIP 带宽大小 | 此选项仅在选择`创建 EIP`时显示。EIP 的带宽。 | -| 身份验证模式 | 表示启用 `RBAC`，或同时启用`认证代理`。如果选择`认证代理`，则还需要用于验证代理的证书。 | -| 节点标签 | 集群节点的标签。无效标签会阻止升级，或阻止 Rancher 启动。有关标签语法的详细信息，请参阅 [Kubernetes 文档](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)。 | \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index dd034e3daf8..0506f1f92e5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher 支持以下 Kubernetes 提供商： - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## 托管 Kubernetes 提供商的认证 @@ -28,6 +25,4 @@ Rancher 支持以下 Kubernetes 提供商： - [创建 GKE 集群](gke.md) - [创建 EKS 集群](eks.md) - [创建 AKS 集群](aks.md) -- [创建 ACK 集群](alibaba.md) -- [创建 TKE 集群](tencent.md) -- [创建 CCE 集群](huawei.md) + diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 13349de2c08..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: 创建腾讯 TKE 集群 ---- - -你可以使用 Rancher 创建托管在腾讯 Tencent Kubernetes Engine (TKE) 中的集群。Rancher 已经为 TKE 实现并打包了针对 TKE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 TKE 集群，你需要[启用 TKE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 TKE 集群。 - -## 腾讯先决条件 - -:::caution - -部署到 TKE 会产生费用。 - -::: - -1. 参见[云访问管理](https://intl.cloud.tencent.com/document/product/598/10600)文档，确保用于创建 TKE 集群的账号具有适当的权限。 - -2. 创建[云 API 密钥 ID 和密钥](https://console.cloud.tencent.com/capi)。 - -3. 在要部署 Kubernetes 集群的区域中创建[私有网络和子网](https://intl.cloud.tencent.com/document/product/215/4927)。 - -4. 创建 [SSH 密钥对](https://intl.cloud.tencent.com/document/product/213/6092)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用腾讯 TKE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Tencent TKE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建腾讯 TKE 集群了。 - -## 创建 TKE 集群 - -1. 在**集群**页面，点击**创建**。 - -2. 选择 **Tencent TKE**。 - -3. 输入**集群名称**。 - -4. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 - -5. 为 TKE 集群配置**账号访问**。使用[先决条件](#腾讯先决条件)中获得的信息完成每个下拉列表和字段。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 区域 | 从下拉列表中选择构建集群的地理区域。 | - | 密文 ID | 输入从腾讯云控制台获取的密文 ID。 | - | 密文密钥 | 输入从腾讯云控制台获取的密文密钥。 | - -6. 然后，单击`下一步：配置集群`来配置 TKE 集群。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes 版本 | TKE 目前只支持 Kubernetes 1.10.5。 | - | 节点数 | 输入要为 Kubernetes 集群购买的 worker 节点数，最大值是 100。 | - | VPC | 选择在腾讯云控制台中创建的 VPC 名称。 | - | 容器网络 CIDR | 输入 Kubernetes 集群的 CIDR 范围。你可以在腾讯云控制台的 VPC 服务中查看该 CIDR 的可用范围。默认为 172.16.0.0/16。 | - - :::note - - 如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅 [Rancher 2.3.0+ 配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - - ::: - -7. 点击`下一步：选择实例类型`，然后选择将用于 TKE 集群的实例类型。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 可用区 | 选择 VPC 区域的可用区。 | - | 子网 | 选择你在 VPC 中创建的子网。如果在所选可用区中没有该子网，请添加一个新子网。 | - | 实例类型 | 从下拉列表中选择要用于 TKE 集群的 VM 实例类型，默认为 S2.MEDIUM4（CPU 2；内存 4 GiB）。 | - -8. 点击`下一步：配置实例`，配置用于 TKE 集群的 VM 实例。 - - | 选项 | 描述 | - -------|------------ - | 操作系统 | 操作系统名称，目前支持 Centos7.2x86_64 或 ubuntu16.04.1 LTSx86_64。 | - | 安全组 | 安全组 ID，默认不绑定任何安全组。 | - | 根磁盘类型 | 系统盘类型。系统盘类型限制详见 [CVM 实例配置](https://cloud.tencent.com/document/product/213/11518)。 | - | 根磁盘大小 | 系统盘大小。Linux 系统调整范围为 20-50 GB，步长为 1。 | - | 数据盘类型 | 数据盘类型，默认为 SSD 云盘。 | - | 数据磁盘大小 | 数据盘大小（GB），步长为 10。 | - | 带宽类型 | 带宽收费类型，PayByTraffic 或 PayByHour。 | - | 带宽 | 公网带宽 (Mbps) | - | 密钥对 | 密钥 ID，关联后可以用来登录 VM 节点。 | - -9. 单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index c10c4b83785..efcd02f34ba 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ Rancher 中有两种类型的驱动： * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -还有几个托管的 Kubernetes 云提供商是默认禁用的，但也打包在 Rancher 中： - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ## 主机驱动 主机驱动用于配置主机，Rancher 使用这些主机启动和管理 Kubernetes 集群。主机驱动与 [Docker Machine 驱动](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md)相同。创建主机模板时可以显示的主机驱动，是由主机驱动的状态定义的。只有 `active` 主机驱动将显示为创建节点模板的选项。默认情况下，Rancher 与许多现有的 Docker Machine 驱动打包在一起，但你也可以创建自定义主机驱动并添加到 Rancher。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index a10200d37fa..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: 创建阿里云 ACK 集群 ---- - -你可以使用 Rancher 创建托管在阿里云 Alibaba Cloud Kubernetes (ACK) 中的集群。Rancher 已经为 ACK 实现并打包了针对 ACK 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 ACK 集群，你需要[启用 ACK 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 ACK 集群。 - -## Rancher 之外的先决条件 - -:::caution - -部署到 ACK 会产生费用。 - -::: - -1. 在阿里云中，在对应的控制台中激活以下服务。 - - - [容器服务](https://cs.console.aliyun.com) - - [资源编排服务](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. 确保你用于创建 ACK 集群的账号具有适当的权限。详见阿里云[角色授权](https://www.alibabacloud.com/help/doc-detail/86483.htm)和[使用容器服务控制台作为 RAM 用户](https://www.alibabacloud.com/help/doc-detail/86484.htm)官方文档。 - -3. 在阿里云中，创建[访问密钥](https://www.alibabacloud.com/help/doc-detail/53045.html)。 - -4. 在阿里云中，创建 [SSH 密钥对](https://www.alibabacloud.com/help/doc-detail/51793.html)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用阿里云 ACK 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Alibaba ACK** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建阿里云 ACK 集群了。 - -## 创建 ACK 集群 - -1. 点击 **☰ > 集群管理**。 -1. 在**集群**页面，点击**创建**。 -1. 单击 **Alibaba ACK**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 为 ACK 集群配置**账号访问**。选择要在其中构建集群的地理区域，并输入在先决条件步骤中创建的访问密钥。 -1. 点击**下一步：配置集群**，然后选择集群类型、Kubernetes 版本和可用区。 -1. 如果选择 **Kubernetes** 作为集群类型，请单击**下一步：配置 master 节点**，然后填写 **master 节点**表单。 -1. 单击**下一步：配置 Worker 节点**，然后填写 **Worker 节点**表单。 -1. 检查并确认你的选项。然后单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index b6244c617d6..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: 创建华为 CCE 集群 ---- - -你可以使用 Rancher 创建托管在华为云容器引擎 (CCE) 中的集群。Rancher 已经为 CCE 实现并打包了针对 CCE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 CCE 集群，你需要[启用 CCE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 CCE 集群。 - -## 华为先决条件 - -:::caution - -部署到 CCE 会产生费用。 - -::: - -1. 在华为 CCE 门户中找到你的项目 ID。请参阅 CCE 文档以了解如何[管理你的项目](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214)。 - -2. 创建一个[访问密钥 ID 和密文访问密钥](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html)。 - -## Rancher 先决条件 - -你需要启用华为 CCE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Huawei CCE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建华为 CCE 集群了。 - -## 限制 - -华为 CCE 服务不支持通过其 API 创建具有公共访问权限的集群。你需要在要配置的 CCE 集群的相同 VPC 中运行 Rancher。 - -## 创建 CCE 集群 - -1. 在**集群**页面，点击**创建**。 -1. 单击 **Huawei CCE**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 输入**项目 ID**，访问密钥 ID，**Access Key**，和密文访问密钥 **Secret Key**。然后点击**下一步：配置集群**。填写集群配置。有关填写表单的帮助，请参阅[华为 CCE 配置](#华为-cce-配置)。 -1. 填写集群的以下节点配置。有关填写表单的帮助，请参阅[节点配置](#节点配置)。 -1. 点击**创建**来创建 CCE 集群。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 - -## 华为 CCE 配置 - -| 设置 | 描述 | -|---|---| -| 集群类型 | 要包含到集群的节点类型，可以是 `VirtualMachine` 或 `BareMetal`。 | -| 描述 | 集群的描述。 | -| 主版本 | Kubernetes 版本。 | -| 管理规模数量 | 集群的最大节点数。选项为 50、200 和 1000。规模计数越大，成本越高。 | -| 高可用性 | 启用 master 节点的高可用性。启用高可用性的集群成本会更高。 | -| 容器网络模式 | 集群中使用的网络模式。`VirtualMachine` 支持 `overlay_l2` 和 `vpc-router`，而 `BareMetal` 支持 `underlay_ipvlan`。 | -| 容器网络 CIDR | 集群的网络 CIDR。 | -| VPC 名称 | 要部署集群的 VPC 名称。如果留空，Rancher 将创建一个。 | -| 子网名称 | 要部署集群的子网名称。如果留空，Rancher 将创建一个。 | -| 外部服务器 | 预留选项，用于通过 API 启用 CCE 集群的公共访问。这个选项暂时是一直禁用的。 | -| 集群标签 | 集群的标签。 | -| 高速子网 | 只有 `BareMetal` 支持该选项。裸机要求选择网速高的 VPC。 | - -:::note - -如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅[配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - -::: - -## 节点配置 - -| 设置 | 描述 | -|---|---| -| 地区 | 部署集群节点的可用区域。 | -| 计费方式 | 集群节点的计费模式。`VirtualMachine` 仅支持 `Pay-per-use`。`BareMetal` 支持 `Pay-per-use` 或 `Yearly/Monthly`。 | -| 有效期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示支付集群节点费用的时间。 | -| 自动续期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示是否为集群节点自动续期 `Yearly/Monthly` 计费。 | -| 数据卷类型 | 集群节点的数据卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 数据量大小 | 集群节点的数据卷大小。 | -| 根卷类型 | 集群节点的根卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 根卷大小 | 集群节点的根卷大小。 | -| 节点风格 | 集群节点的节点风格。Rancher UI 中的风格列表取自华为云。其中包括所有支持的节点风格。 | -| 节点数 | 集群的节点数 | -| 节点操作系统 | 集群节点的操作系统。目前仅支持 `EulerOS 2.2` 和 `CentOS 7.4`。 | -| SSH 密钥名称 | 集群节点的 SSH 密钥 | -| EIP | 集群节点的公共 IP 选项。`已禁用`表示集群节点不会绑定公共 IP。`创建 EIP`表示集群节点在配置后将绑定一个或多个新创建的 EIP，UI 中将显示更多用来创建 EIP 参数的选项。`选择现有 EIP` 表示节点将绑定到你选择的 EIP。 | -| EIP 数量 | 此选项仅在选择`创建 EIP`时显示。表示你要为节点创建的 EIP 数量。 | -| EIP 类型 | 此选项仅在选择`创建 EIP`时显示。可选 `5_bgp` 和 `5_sbgp`。 | -| EIP 共享类型 | 此选项仅在选择`创建 EIP`时显示。仅可选 `PER`。 | -| EIP 收费模式 | 此选项仅在选择`创建 EIP`时显示。选择按照`带宽`或`流量`计费。 | -| EIP 带宽大小 | 此选项仅在选择`创建 EIP`时显示。EIP 的带宽。 | -| 身份验证模式 | 表示启用 `RBAC`，或同时启用`认证代理`。如果选择`认证代理`，则还需要用于验证代理的证书。 | -| 节点标签 | 集群节点的标签。无效标签会阻止升级，或阻止 Rancher 启动。有关标签语法的详细信息，请参阅 [Kubernetes 文档](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)。 | \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index dd034e3daf8..0506f1f92e5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher 支持以下 Kubernetes 提供商： - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## 托管 Kubernetes 提供商的认证 @@ -28,6 +25,4 @@ Rancher 支持以下 Kubernetes 提供商： - [创建 GKE 集群](gke.md) - [创建 EKS 集群](eks.md) - [创建 AKS 集群](aks.md) -- [创建 ACK 集群](alibaba.md) -- [创建 TKE 集群](tencent.md) -- [创建 CCE 集群](huawei.md) + diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 13349de2c08..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: 创建腾讯 TKE 集群 ---- - -你可以使用 Rancher 创建托管在腾讯 Tencent Kubernetes Engine (TKE) 中的集群。Rancher 已经为 TKE 实现并打包了针对 TKE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 TKE 集群，你需要[启用 TKE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 TKE 集群。 - -## 腾讯先决条件 - -:::caution - -部署到 TKE 会产生费用。 - -::: - -1. 参见[云访问管理](https://intl.cloud.tencent.com/document/product/598/10600)文档，确保用于创建 TKE 集群的账号具有适当的权限。 - -2. 创建[云 API 密钥 ID 和密钥](https://console.cloud.tencent.com/capi)。 - -3. 在要部署 Kubernetes 集群的区域中创建[私有网络和子网](https://intl.cloud.tencent.com/document/product/215/4927)。 - -4. 创建 [SSH 密钥对](https://intl.cloud.tencent.com/document/product/213/6092)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用腾讯 TKE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Tencent TKE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建腾讯 TKE 集群了。 - -## 创建 TKE 集群 - -1. 在**集群**页面，点击**创建**。 - -2. 选择 **Tencent TKE**。 - -3. 输入**集群名称**。 - -4. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 - -5. 为 TKE 集群配置**账号访问**。使用[先决条件](#腾讯先决条件)中获得的信息完成每个下拉列表和字段。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 区域 | 从下拉列表中选择构建集群的地理区域。 | - | 密文 ID | 输入从腾讯云控制台获取的密文 ID。 | - | 密文密钥 | 输入从腾讯云控制台获取的密文密钥。 | - -6. 然后，单击`下一步：配置集群`来配置 TKE 集群。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes 版本 | TKE 目前只支持 Kubernetes 1.10.5。 | - | 节点数 | 输入要为 Kubernetes 集群购买的 worker 节点数，最大值是 100。 | - | VPC | 选择在腾讯云控制台中创建的 VPC 名称。 | - | 容器网络 CIDR | 输入 Kubernetes 集群的 CIDR 范围。你可以在腾讯云控制台的 VPC 服务中查看该 CIDR 的可用范围。默认为 172.16.0.0/16。 | - - :::note - - 如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅 [Rancher 2.3.0+ 配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - - ::: - -7. 点击`下一步：选择实例类型`，然后选择将用于 TKE 集群的实例类型。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 可用区 | 选择 VPC 区域的可用区。 | - | 子网 | 选择你在 VPC 中创建的子网。如果在所选可用区中没有该子网，请添加一个新子网。 | - | 实例类型 | 从下拉列表中选择要用于 TKE 集群的 VM 实例类型，默认为 S2.MEDIUM4（CPU 2；内存 4 GiB）。 | - -8. 点击`下一步：配置实例`，配置用于 TKE 集群的 VM 实例。 - - | 选项 | 描述 | - -------|------------ - | 操作系统 | 操作系统名称，目前支持 Centos7.2x86_64 或 ubuntu16.04.1 LTSx86_64。 | - | 安全组 | 安全组 ID，默认不绑定任何安全组。 | - | 根磁盘类型 | 系统盘类型。系统盘类型限制详见 [CVM 实例配置](https://cloud.tencent.com/document/product/213/11518)。 | - | 根磁盘大小 | 系统盘大小。Linux 系统调整范围为 20-50 GB，步长为 1。 | - | 数据盘类型 | 数据盘类型，默认为 SSD 云盘。 | - | 数据磁盘大小 | 数据盘大小（GB），步长为 10。 | - | 带宽类型 | 带宽收费类型，PayByTraffic 或 PayByHour。 | - | 带宽 | 公网带宽 (Mbps) | - | 密钥对 | 密钥 ID，关联后可以用来登录 VM 节点。 | - -9. 单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index c10c4b83785..efcd02f34ba 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ Rancher 中有两种类型的驱动： * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -还有几个托管的 Kubernetes 云提供商是默认禁用的，但也打包在 Rancher 中： - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ## 主机驱动 主机驱动用于配置主机，Rancher 使用这些主机启动和管理 Kubernetes 集群。主机驱动与 [Docker Machine 驱动](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md)相同。创建主机模板时可以显示的主机驱动，是由主机驱动的状态定义的。只有 `active` 主机驱动将显示为创建节点模板的选项。默认情况下，Rancher 与许多现有的 Docker Machine 驱动打包在一起，但你也可以创建自定义主机驱动并添加到 Rancher。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index a10200d37fa..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: 创建阿里云 ACK 集群 ---- - -你可以使用 Rancher 创建托管在阿里云 Alibaba Cloud Kubernetes (ACK) 中的集群。Rancher 已经为 ACK 实现并打包了针对 ACK 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 ACK 集群，你需要[启用 ACK 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 ACK 集群。 - -## Rancher 之外的先决条件 - -:::caution - -部署到 ACK 会产生费用。 - -::: - -1. 在阿里云中，在对应的控制台中激活以下服务。 - - - [容器服务](https://cs.console.aliyun.com) - - [资源编排服务](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. 确保你用于创建 ACK 集群的账号具有适当的权限。详见阿里云[角色授权](https://www.alibabacloud.com/help/doc-detail/86483.htm)和[使用容器服务控制台作为 RAM 用户](https://www.alibabacloud.com/help/doc-detail/86484.htm)官方文档。 - -3. 在阿里云中，创建[访问密钥](https://www.alibabacloud.com/help/doc-detail/53045.html)。 - -4. 在阿里云中，创建 [SSH 密钥对](https://www.alibabacloud.com/help/doc-detail/51793.html)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用阿里云 ACK 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Alibaba ACK** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建阿里云 ACK 集群了。 - -## 创建 ACK 集群 - -1. 点击 **☰ > 集群管理**。 -1. 在**集群**页面，点击**创建**。 -1. 单击 **Alibaba ACK**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 为 ACK 集群配置**账号访问**。选择要在其中构建集群的地理区域，并输入在先决条件步骤中创建的访问密钥。 -1. 点击**下一步：配置集群**，然后选择集群类型、Kubernetes 版本和可用区。 -1. 如果选择 **Kubernetes** 作为集群类型，请单击**下一步：配置 master 节点**，然后填写 **master 节点**表单。 -1. 单击**下一步：配置 Worker 节点**，然后填写 **Worker 节点**表单。 -1. 检查并确认你的选项。然后单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index b6244c617d6..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: 创建华为 CCE 集群 ---- - -你可以使用 Rancher 创建托管在华为云容器引擎 (CCE) 中的集群。Rancher 已经为 CCE 实现并打包了针对 CCE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 CCE 集群，你需要[启用 CCE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 CCE 集群。 - -## 华为先决条件 - -:::caution - -部署到 CCE 会产生费用。 - -::: - -1. 在华为 CCE 门户中找到你的项目 ID。请参阅 CCE 文档以了解如何[管理你的项目](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214)。 - -2. 创建一个[访问密钥 ID 和密文访问密钥](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html)。 - -## Rancher 先决条件 - -你需要启用华为 CCE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Huawei CCE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建华为 CCE 集群了。 - -## 限制 - -华为 CCE 服务不支持通过其 API 创建具有公共访问权限的集群。你需要在要配置的 CCE 集群的相同 VPC 中运行 Rancher。 - -## 创建 CCE 集群 - -1. 在**集群**页面，点击**创建**。 -1. 单击 **Huawei CCE**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 输入**项目 ID**，访问密钥 ID，**Access Key**，和密文访问密钥 **Secret Key**。然后点击**下一步：配置集群**。填写集群配置。有关填写表单的帮助，请参阅[华为 CCE 配置](#华为-cce-配置)。 -1. 填写集群的以下节点配置。有关填写表单的帮助，请参阅[节点配置](#节点配置)。 -1. 点击**创建**来创建 CCE 集群。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 - -## 华为 CCE 配置 - -| 设置 | 描述 | -|---|---| -| 集群类型 | 要包含到集群的节点类型，可以是 `VirtualMachine` 或 `BareMetal`。 | -| 描述 | 集群的描述。 | -| 主版本 | Kubernetes 版本。 | -| 管理规模数量 | 集群的最大节点数。选项为 50、200 和 1000。规模计数越大，成本越高。 | -| 高可用性 | 启用 master 节点的高可用性。启用高可用性的集群成本会更高。 | -| 容器网络模式 | 集群中使用的网络模式。`VirtualMachine` 支持 `overlay_l2` 和 `vpc-router`，而 `BareMetal` 支持 `underlay_ipvlan`。 | -| 容器网络 CIDR | 集群的网络 CIDR。 | -| VPC 名称 | 要部署集群的 VPC 名称。如果留空，Rancher 将创建一个。 | -| 子网名称 | 要部署集群的子网名称。如果留空，Rancher 将创建一个。 | -| 外部服务器 | 预留选项，用于通过 API 启用 CCE 集群的公共访问。这个选项暂时是一直禁用的。 | -| 集群标签 | 集群的标签。 | -| 高速子网 | 只有 `BareMetal` 支持该选项。裸机要求选择网速高的 VPC。 | - -:::note - -如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅[配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - -::: - -## 节点配置 - -| 设置 | 描述 | -|---|---| -| 地区 | 部署集群节点的可用区域。 | -| 计费方式 | 集群节点的计费模式。`VirtualMachine` 仅支持 `Pay-per-use`。`BareMetal` 支持 `Pay-per-use` 或 `Yearly/Monthly`。 | -| 有效期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示支付集群节点费用的时间。 | -| 自动续期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示是否为集群节点自动续期 `Yearly/Monthly` 计费。 | -| 数据卷类型 | 集群节点的数据卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 数据量大小 | 集群节点的数据卷大小。 | -| 根卷类型 | 集群节点的根卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 根卷大小 | 集群节点的根卷大小。 | -| 节点风格 | 集群节点的节点风格。Rancher UI 中的风格列表取自华为云。其中包括所有支持的节点风格。 | -| 节点数 | 集群的节点数 | -| 节点操作系统 | 集群节点的操作系统。目前仅支持 `EulerOS 2.2` 和 `CentOS 7.4`。 | -| SSH 密钥名称 | 集群节点的 SSH 密钥 | -| EIP | 集群节点的公共 IP 选项。`已禁用`表示集群节点不会绑定公共 IP。`创建 EIP`表示集群节点在配置后将绑定一个或多个新创建的 EIP，UI 中将显示更多用来创建 EIP 参数的选项。`选择现有 EIP` 表示节点将绑定到你选择的 EIP。 | -| EIP 数量 | 此选项仅在选择`创建 EIP`时显示。表示你要为节点创建的 EIP 数量。 | -| EIP 类型 | 此选项仅在选择`创建 EIP`时显示。可选 `5_bgp` 和 `5_sbgp`。 | -| EIP 共享类型 | 此选项仅在选择`创建 EIP`时显示。仅可选 `PER`。 | -| EIP 收费模式 | 此选项仅在选择`创建 EIP`时显示。选择按照`带宽`或`流量`计费。 | -| EIP 带宽大小 | 此选项仅在选择`创建 EIP`时显示。EIP 的带宽。 | -| 身份验证模式 | 表示启用 `RBAC`，或同时启用`认证代理`。如果选择`认证代理`，则还需要用于验证代理的证书。 | -| 节点标签 | 集群节点的标签。无效标签会阻止升级，或阻止 Rancher 启动。有关标签语法的详细信息，请参阅 [Kubernetes 文档](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)。 | \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index dd034e3daf8..b034f3df70a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher 支持以下 Kubernetes 提供商： - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## 托管 Kubernetes 提供商的认证 @@ -28,6 +25,3 @@ Rancher 支持以下 Kubernetes 提供商： - [创建 GKE 集群](gke.md) - [创建 EKS 集群](eks.md) - [创建 AKS 集群](aks.md) -- [创建 ACK 集群](alibaba.md) -- [创建 TKE 集群](tencent.md) -- [创建 CCE 集群](huawei.md) diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 13349de2c08..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: 创建腾讯 TKE 集群 ---- - -你可以使用 Rancher 创建托管在腾讯 Tencent Kubernetes Engine (TKE) 中的集群。Rancher 已经为 TKE 实现并打包了针对 TKE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 TKE 集群，你需要[启用 TKE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 TKE 集群。 - -## 腾讯先决条件 - -:::caution - -部署到 TKE 会产生费用。 - -::: - -1. 参见[云访问管理](https://intl.cloud.tencent.com/document/product/598/10600)文档，确保用于创建 TKE 集群的账号具有适当的权限。 - -2. 创建[云 API 密钥 ID 和密钥](https://console.cloud.tencent.com/capi)。 - -3. 在要部署 Kubernetes 集群的区域中创建[私有网络和子网](https://intl.cloud.tencent.com/document/product/215/4927)。 - -4. 创建 [SSH 密钥对](https://intl.cloud.tencent.com/document/product/213/6092)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用腾讯 TKE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Tencent TKE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建腾讯 TKE 集群了。 - -## 创建 TKE 集群 - -1. 在**集群**页面，点击**创建**。 - -2. 选择 **Tencent TKE**。 - -3. 输入**集群名称**。 - -4. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 - -5. 为 TKE 集群配置**账号访问**。使用[先决条件](#腾讯先决条件)中获得的信息完成每个下拉列表和字段。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 区域 | 从下拉列表中选择构建集群的地理区域。 | - | 密文 ID | 输入从腾讯云控制台获取的密文 ID。 | - | 密文密钥 | 输入从腾讯云控制台获取的密文密钥。 | - -6. 然后，单击`下一步：配置集群`来配置 TKE 集群。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes 版本 | TKE 目前只支持 Kubernetes 1.10.5。 | - | 节点数 | 输入要为 Kubernetes 集群购买的 worker 节点数，最大值是 100。 | - | VPC | 选择在腾讯云控制台中创建的 VPC 名称。 | - | 容器网络 CIDR | 输入 Kubernetes 集群的 CIDR 范围。你可以在腾讯云控制台的 VPC 服务中查看该 CIDR 的可用范围。默认为 172.16.0.0/16。 | - - :::note - - 如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅 [Rancher 2.3.0+ 配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - - ::: - -7. 点击`下一步：选择实例类型`，然后选择将用于 TKE 集群的实例类型。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 可用区 | 选择 VPC 区域的可用区。 | - | 子网 | 选择你在 VPC 中创建的子网。如果在所选可用区中没有该子网，请添加一个新子网。 | - | 实例类型 | 从下拉列表中选择要用于 TKE 集群的 VM 实例类型，默认为 S2.MEDIUM4（CPU 2；内存 4 GiB）。 | - -8. 点击`下一步：配置实例`，配置用于 TKE 集群的 VM 实例。 - - | 选项 | 描述 | - -------|------------ - | 操作系统 | 操作系统名称，目前支持 Centos7.2x86_64 或 ubuntu16.04.1 LTSx86_64。 | - | 安全组 | 安全组 ID，默认不绑定任何安全组。 | - | 根磁盘类型 | 系统盘类型。系统盘类型限制详见 [CVM 实例配置](https://cloud.tencent.com/document/product/213/11518)。 | - | 根磁盘大小 | 系统盘大小。Linux 系统调整范围为 20-50 GB，步长为 1。 | - | 数据盘类型 | 数据盘类型，默认为 SSD 云盘。 | - | 数据磁盘大小 | 数据盘大小（GB），步长为 10。 | - | 带宽类型 | 带宽收费类型，PayByTraffic 或 PayByHour。 | - | 带宽 | 公网带宽 (Mbps) | - | 密钥对 | 密钥 ID，关联后可以用来登录 VM 节点。 | - -9. 单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index c10c4b83785..efcd02f34ba 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ Rancher 中有两种类型的驱动： * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -还有几个托管的 Kubernetes 云提供商是默认禁用的，但也打包在 Rancher 中： - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ## 主机驱动 主机驱动用于配置主机，Rancher 使用这些主机启动和管理 Kubernetes 集群。主机驱动与 [Docker Machine 驱动](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md)相同。创建主机模板时可以显示的主机驱动，是由主机驱动的状态定义的。只有 `active` 主机驱动将显示为创建节点模板的选项。默认情况下，Rancher 与许多现有的 Docker Machine 驱动打包在一起，但你也可以创建自定义主机驱动并添加到 Rancher。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index a10200d37fa..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: 创建阿里云 ACK 集群 ---- - -你可以使用 Rancher 创建托管在阿里云 Alibaba Cloud Kubernetes (ACK) 中的集群。Rancher 已经为 ACK 实现并打包了针对 ACK 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 ACK 集群，你需要[启用 ACK 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 ACK 集群。 - -## Rancher 之外的先决条件 - -:::caution - -部署到 ACK 会产生费用。 - -::: - -1. 在阿里云中，在对应的控制台中激活以下服务。 - - - [容器服务](https://cs.console.aliyun.com) - - [资源编排服务](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. 确保你用于创建 ACK 集群的账号具有适当的权限。详见阿里云[角色授权](https://www.alibabacloud.com/help/doc-detail/86483.htm)和[使用容器服务控制台作为 RAM 用户](https://www.alibabacloud.com/help/doc-detail/86484.htm)官方文档。 - -3. 在阿里云中，创建[访问密钥](https://www.alibabacloud.com/help/doc-detail/53045.html)。 - -4. 在阿里云中，创建 [SSH 密钥对](https://www.alibabacloud.com/help/doc-detail/51793.html)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用阿里云 ACK 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Alibaba ACK** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建阿里云 ACK 集群了。 - -## 创建 ACK 集群 - -1. 点击 **☰ > 集群管理**。 -1. 在**集群**页面，点击**创建**。 -1. 单击 **Alibaba ACK**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 为 ACK 集群配置**账号访问**。选择要在其中构建集群的地理区域，并输入在先决条件步骤中创建的访问密钥。 -1. 点击**下一步：配置集群**，然后选择集群类型、Kubernetes 版本和可用区。 -1. 如果选择 **Kubernetes** 作为集群类型，请单击**下一步：配置 master 节点**，然后填写 **master 节点**表单。 -1. 单击**下一步：配置 Worker 节点**，然后填写 **Worker 节点**表单。 -1. 检查并确认你的选项。然后单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index b6244c617d6..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: 创建华为 CCE 集群 ---- - -你可以使用 Rancher 创建托管在华为云容器引擎 (CCE) 中的集群。Rancher 已经为 CCE 实现并打包了针对 CCE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 CCE 集群，你需要[启用 CCE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 CCE 集群。 - -## 华为先决条件 - -:::caution - -部署到 CCE 会产生费用。 - -::: - -1. 在华为 CCE 门户中找到你的项目 ID。请参阅 CCE 文档以了解如何[管理你的项目](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214)。 - -2. 创建一个[访问密钥 ID 和密文访问密钥](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html)。 - -## Rancher 先决条件 - -你需要启用华为 CCE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Huawei CCE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建华为 CCE 集群了。 - -## 限制 - -华为 CCE 服务不支持通过其 API 创建具有公共访问权限的集群。你需要在要配置的 CCE 集群的相同 VPC 中运行 Rancher。 - -## 创建 CCE 集群 - -1. 在**集群**页面，点击**创建**。 -1. 单击 **Huawei CCE**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 输入**项目 ID**，访问密钥 ID，**Access Key**，和密文访问密钥 **Secret Key**。然后点击**下一步：配置集群**。填写集群配置。有关填写表单的帮助，请参阅[华为 CCE 配置](#华为-cce-配置)。 -1. 填写集群的以下节点配置。有关填写表单的帮助，请参阅[节点配置](#节点配置)。 -1. 点击**创建**来创建 CCE 集群。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 - -## 华为 CCE 配置 - -| 设置 | 描述 | -|---|---| -| 集群类型 | 要包含到集群的节点类型，可以是 `VirtualMachine` 或 `BareMetal`。 | -| 描述 | 集群的描述。 | -| 主版本 | Kubernetes 版本。 | -| 管理规模数量 | 集群的最大节点数。选项为 50、200 和 1000。规模计数越大，成本越高。 | -| 高可用性 | 启用 master 节点的高可用性。启用高可用性的集群成本会更高。 | -| 容器网络模式 | 集群中使用的网络模式。`VirtualMachine` 支持 `overlay_l2` 和 `vpc-router`，而 `BareMetal` 支持 `underlay_ipvlan`。 | -| 容器网络 CIDR | 集群的网络 CIDR。 | -| VPC 名称 | 要部署集群的 VPC 名称。如果留空，Rancher 将创建一个。 | -| 子网名称 | 要部署集群的子网名称。如果留空，Rancher 将创建一个。 | -| 外部服务器 | 预留选项，用于通过 API 启用 CCE 集群的公共访问。这个选项暂时是一直禁用的。 | -| 集群标签 | 集群的标签。 | -| 高速子网 | 只有 `BareMetal` 支持该选项。裸机要求选择网速高的 VPC。 | - -:::note - -如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅[配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - -::: - -## 节点配置 - -| 设置 | 描述 | -|---|---| -| 地区 | 部署集群节点的可用区域。 | -| 计费方式 | 集群节点的计费模式。`VirtualMachine` 仅支持 `Pay-per-use`。`BareMetal` 支持 `Pay-per-use` 或 `Yearly/Monthly`。 | -| 有效期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示支付集群节点费用的时间。 | -| 自动续期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示是否为集群节点自动续期 `Yearly/Monthly` 计费。 | -| 数据卷类型 | 集群节点的数据卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 数据量大小 | 集群节点的数据卷大小。 | -| 根卷类型 | 集群节点的根卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 根卷大小 | 集群节点的根卷大小。 | -| 节点风格 | 集群节点的节点风格。Rancher UI 中的风格列表取自华为云。其中包括所有支持的节点风格。 | -| 节点数 | 集群的节点数 | -| 节点操作系统 | 集群节点的操作系统。目前仅支持 `EulerOS 2.2` 和 `CentOS 7.4`。 | -| SSH 密钥名称 | 集群节点的 SSH 密钥 | -| EIP | 集群节点的公共 IP 选项。`已禁用`表示集群节点不会绑定公共 IP。`创建 EIP`表示集群节点在配置后将绑定一个或多个新创建的 EIP，UI 中将显示更多用来创建 EIP 参数的选项。`选择现有 EIP` 表示节点将绑定到你选择的 EIP。 | -| EIP 数量 | 此选项仅在选择`创建 EIP`时显示。表示你要为节点创建的 EIP 数量。 | -| EIP 类型 | 此选项仅在选择`创建 EIP`时显示。可选 `5_bgp` 和 `5_sbgp`。 | -| EIP 共享类型 | 此选项仅在选择`创建 EIP`时显示。仅可选 `PER`。 | -| EIP 收费模式 | 此选项仅在选择`创建 EIP`时显示。选择按照`带宽`或`流量`计费。 | -| EIP 带宽大小 | 此选项仅在选择`创建 EIP`时显示。EIP 的带宽。 | -| 身份验证模式 | 表示启用 `RBAC`，或同时启用`认证代理`。如果选择`认证代理`，则还需要用于验证代理的证书。 | -| 节点标签 | 集群节点的标签。无效标签会阻止升级，或阻止 Rancher 启动。有关标签语法的详细信息，请参阅 [Kubernetes 文档](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)。 | \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index dd034e3daf8..0506f1f92e5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher 支持以下 Kubernetes 提供商： - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## 托管 Kubernetes 提供商的认证 @@ -28,6 +25,4 @@ Rancher 支持以下 Kubernetes 提供商： - [创建 GKE 集群](gke.md) - [创建 EKS 集群](eks.md) - [创建 AKS 集群](aks.md) -- [创建 ACK 集群](alibaba.md) -- [创建 TKE 集群](tencent.md) -- [创建 CCE 集群](huawei.md) + diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 13349de2c08..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: 创建腾讯 TKE 集群 ---- - -你可以使用 Rancher 创建托管在腾讯 Tencent Kubernetes Engine (TKE) 中的集群。Rancher 已经为 TKE 实现并打包了针对 TKE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 TKE 集群，你需要[启用 TKE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 TKE 集群。 - -## 腾讯先决条件 - -:::caution - -部署到 TKE 会产生费用。 - -::: - -1. 参见[云访问管理](https://intl.cloud.tencent.com/document/product/598/10600)文档，确保用于创建 TKE 集群的账号具有适当的权限。 - -2. 创建[云 API 密钥 ID 和密钥](https://console.cloud.tencent.com/capi)。 - -3. 在要部署 Kubernetes 集群的区域中创建[私有网络和子网](https://intl.cloud.tencent.com/document/product/215/4927)。 - -4. 创建 [SSH 密钥对](https://intl.cloud.tencent.com/document/product/213/6092)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用腾讯 TKE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Tencent TKE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建腾讯 TKE 集群了。 - -## 创建 TKE 集群 - -1. 在**集群**页面，点击**创建**。 - -2. 选择 **Tencent TKE**。 - -3. 输入**集群名称**。 - -4. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 - -5. 为 TKE 集群配置**账号访问**。使用[先决条件](#腾讯先决条件)中获得的信息完成每个下拉列表和字段。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 区域 | 从下拉列表中选择构建集群的地理区域。 | - | 密文 ID | 输入从腾讯云控制台获取的密文 ID。 | - | 密文密钥 | 输入从腾讯云控制台获取的密文密钥。 | - -6. 然后，单击`下一步：配置集群`来配置 TKE 集群。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes 版本 | TKE 目前只支持 Kubernetes 1.10.5。 | - | 节点数 | 输入要为 Kubernetes 集群购买的 worker 节点数，最大值是 100。 | - | VPC | 选择在腾讯云控制台中创建的 VPC 名称。 | - | 容器网络 CIDR | 输入 Kubernetes 集群的 CIDR 范围。你可以在腾讯云控制台的 VPC 服务中查看该 CIDR 的可用范围。默认为 172.16.0.0/16。 | - - :::note - - 如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅 [Rancher 2.3.0+ 配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - - ::: - -7. 点击`下一步：选择实例类型`，然后选择将用于 TKE 集群的实例类型。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 可用区 | 选择 VPC 区域的可用区。 | - | 子网 | 选择你在 VPC 中创建的子网。如果在所选可用区中没有该子网，请添加一个新子网。 | - | 实例类型 | 从下拉列表中选择要用于 TKE 集群的 VM 实例类型，默认为 S2.MEDIUM4（CPU 2；内存 4 GiB）。 | - -8. 点击`下一步：配置实例`，配置用于 TKE 集群的 VM 实例。 - - | 选项 | 描述 | - -------|------------ - | 操作系统 | 操作系统名称，目前支持 Centos7.2x86_64 或 ubuntu16.04.1 LTSx86_64。 | - | 安全组 | 安全组 ID，默认不绑定任何安全组。 | - | 根磁盘类型 | 系统盘类型。系统盘类型限制详见 [CVM 实例配置](https://cloud.tencent.com/document/product/213/11518)。 | - | 根磁盘大小 | 系统盘大小。Linux 系统调整范围为 20-50 GB，步长为 1。 | - | 数据盘类型 | 数据盘类型，默认为 SSD 云盘。 | - | 数据磁盘大小 | 数据盘大小（GB），步长为 10。 | - | 带宽类型 | 带宽收费类型，PayByTraffic 或 PayByHour。 | - | 带宽 | 公网带宽 (Mbps) | - | 密钥对 | 密钥 ID，关联后可以用来登录 VM 节点。 | - -9. 单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index 278cd6a56e9..2592c1bff12 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ Rancher 中有两种类型的驱动： * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -还有几个托管的 Kubernetes 云提供商是默认禁用的，但也打包在 Rancher 中： - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ### 主机驱动 主机驱动用于配置主机，Rancher 使用这些主机启动和管理 Kubernetes 集群。主机驱动与 [Docker Machine 驱动](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md)相同。创建主机模板时可以显示的主机驱动，是由主机驱动的状态定义的。只有 `active` 主机驱动将显示为创建节点模板的选项。默认情况下，Rancher 与许多现有的 Docker Machine 驱动打包在一起，但你也可以创建自定义主机驱动并添加到 Rancher。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index a10200d37fa..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: 创建阿里云 ACK 集群 ---- - -你可以使用 Rancher 创建托管在阿里云 Alibaba Cloud Kubernetes (ACK) 中的集群。Rancher 已经为 ACK 实现并打包了针对 ACK 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 ACK 集群，你需要[启用 ACK 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 ACK 集群。 - -## Rancher 之外的先决条件 - -:::caution - -部署到 ACK 会产生费用。 - -::: - -1. 在阿里云中，在对应的控制台中激活以下服务。 - - - [容器服务](https://cs.console.aliyun.com) - - [资源编排服务](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. 确保你用于创建 ACK 集群的账号具有适当的权限。详见阿里云[角色授权](https://www.alibabacloud.com/help/doc-detail/86483.htm)和[使用容器服务控制台作为 RAM 用户](https://www.alibabacloud.com/help/doc-detail/86484.htm)官方文档。 - -3. 在阿里云中，创建[访问密钥](https://www.alibabacloud.com/help/doc-detail/53045.html)。 - -4. 在阿里云中，创建 [SSH 密钥对](https://www.alibabacloud.com/help/doc-detail/51793.html)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用阿里云 ACK 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Alibaba ACK** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建阿里云 ACK 集群了。 - -## 创建 ACK 集群 - -1. 点击 **☰ > 集群管理**。 -1. 在**集群**页面，点击**创建**。 -1. 单击 **Alibaba ACK**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 为 ACK 集群配置**账号访问**。选择要在其中构建集群的地理区域，并输入在先决条件步骤中创建的访问密钥。 -1. 点击**下一步：配置集群**，然后选择集群类型、Kubernetes 版本和可用区。 -1. 如果选择 **Kubernetes** 作为集群类型，请单击**下一步：配置 master 节点**，然后填写 **master 节点**表单。 -1. 单击**下一步：配置 Worker 节点**，然后填写 **Worker 节点**表单。 -1. 检查并确认你的选项。然后单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index b6244c617d6..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: 创建华为 CCE 集群 ---- - -你可以使用 Rancher 创建托管在华为云容器引擎 (CCE) 中的集群。Rancher 已经为 CCE 实现并打包了针对 CCE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 CCE 集群，你需要[启用 CCE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 CCE 集群。 - -## 华为先决条件 - -:::caution - -部署到 CCE 会产生费用。 - -::: - -1. 在华为 CCE 门户中找到你的项目 ID。请参阅 CCE 文档以了解如何[管理你的项目](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214)。 - -2. 创建一个[访问密钥 ID 和密文访问密钥](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html)。 - -## Rancher 先决条件 - -你需要启用华为 CCE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Huawei CCE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建华为 CCE 集群了。 - -## 限制 - -华为 CCE 服务不支持通过其 API 创建具有公共访问权限的集群。你需要在要配置的 CCE 集群的相同 VPC 中运行 Rancher。 - -## 创建 CCE 集群 - -1. 在**集群**页面，点击**创建**。 -1. 单击 **Huawei CCE**。 -1. 输入**集群名称**。 -1. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 -1. 输入**项目 ID**，访问密钥 ID，**Access Key**，和密文访问密钥 **Secret Key**。然后点击**下一步：配置集群**。填写集群配置。有关填写表单的帮助，请参阅[华为 CCE 配置](#华为-cce-配置)。 -1. 填写集群的以下节点配置。有关填写表单的帮助，请参阅[节点配置](#节点配置)。 -1. 点击**创建**来创建 CCE 集群。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 - -## 华为 CCE 配置 - -| 设置 | 描述 | -|---|---| -| 集群类型 | 要包含到集群的节点类型，可以是 `VirtualMachine` 或 `BareMetal`。 | -| 描述 | 集群的描述。 | -| 主版本 | Kubernetes 版本。 | -| 管理规模数量 | 集群的最大节点数。选项为 50、200 和 1000。规模计数越大，成本越高。 | -| 高可用性 | 启用 master 节点的高可用性。启用高可用性的集群成本会更高。 | -| 容器网络模式 | 集群中使用的网络模式。`VirtualMachine` 支持 `overlay_l2` 和 `vpc-router`，而 `BareMetal` 支持 `underlay_ipvlan`。 | -| 容器网络 CIDR | 集群的网络 CIDR。 | -| VPC 名称 | 要部署集群的 VPC 名称。如果留空，Rancher 将创建一个。 | -| 子网名称 | 要部署集群的子网名称。如果留空，Rancher 将创建一个。 | -| 外部服务器 | 预留选项，用于通过 API 启用 CCE 集群的公共访问。这个选项暂时是一直禁用的。 | -| 集群标签 | 集群的标签。 | -| 高速子网 | 只有 `BareMetal` 支持该选项。裸机要求选择网速高的 VPC。 | - -:::note - -如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅[配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - -::: - -## 节点配置 - -| 设置 | 描述 | -|---|---| -| 地区 | 部署集群节点的可用区域。 | -| 计费方式 | 集群节点的计费模式。`VirtualMachine` 仅支持 `Pay-per-use`。`BareMetal` 支持 `Pay-per-use` 或 `Yearly/Monthly`。 | -| 有效期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示支付集群节点费用的时间。 | -| 自动续期 | 该选项仅在 `Yearly/Monthly` 计费模式中显示。表示是否为集群节点自动续期 `Yearly/Monthly` 计费。 | -| 数据卷类型 | 集群节点的数据卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 数据量大小 | 集群节点的数据卷大小。 | -| 根卷类型 | 集群节点的根卷类型。可选 `SATA`，`SSD` 或 `SAS`。 | -| 根卷大小 | 集群节点的根卷大小。 | -| 节点风格 | 集群节点的节点风格。Rancher UI 中的风格列表取自华为云。其中包括所有支持的节点风格。 | -| 节点数 | 集群的节点数 | -| 节点操作系统 | 集群节点的操作系统。目前仅支持 `EulerOS 2.2` 和 `CentOS 7.4`。 | -| SSH 密钥名称 | 集群节点的 SSH 密钥 | -| EIP | 集群节点的公共 IP 选项。`已禁用`表示集群节点不会绑定公共 IP。`创建 EIP`表示集群节点在配置后将绑定一个或多个新创建的 EIP，UI 中将显示更多用来创建 EIP 参数的选项。`选择现有 EIP` 表示节点将绑定到你选择的 EIP。 | -| EIP 数量 | 此选项仅在选择`创建 EIP`时显示。表示你要为节点创建的 EIP 数量。 | -| EIP 类型 | 此选项仅在选择`创建 EIP`时显示。可选 `5_bgp` 和 `5_sbgp`。 | -| EIP 共享类型 | 此选项仅在选择`创建 EIP`时显示。仅可选 `PER`。 | -| EIP 收费模式 | 此选项仅在选择`创建 EIP`时显示。选择按照`带宽`或`流量`计费。 | -| EIP 带宽大小 | 此选项仅在选择`创建 EIP`时显示。EIP 的带宽。 | -| 身份验证模式 | 表示启用 `RBAC`，或同时启用`认证代理`。如果选择`认证代理`，则还需要用于验证代理的证书。 | -| 节点标签 | 集群节点的标签。无效标签会阻止升级，或阻止 Rancher 启动。有关标签语法的详细信息，请参阅 [Kubernetes 文档](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set)。 | \ No newline at end of file diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index dd034e3daf8..0506f1f92e5 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher 支持以下 Kubernetes 提供商： - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## 托管 Kubernetes 提供商的认证 @@ -28,6 +25,4 @@ Rancher 支持以下 Kubernetes 提供商： - [创建 GKE 集群](gke.md) - [创建 EKS 集群](eks.md) - [创建 AKS 集群](aks.md) -- [创建 ACK 集群](alibaba.md) -- [创建 TKE 集群](tencent.md) -- [创建 CCE 集群](huawei.md) + diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 13349de2c08..00000000000 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -title: 创建腾讯 TKE 集群 ---- - -你可以使用 Rancher 创建托管在腾讯 Tencent Kubernetes Engine (TKE) 中的集群。Rancher 已经为 TKE 实现并打包了针对 TKE 的[集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md)，但是默认情况下，这个集群驱动的状态是 `inactive`。为了启动 TKE 集群，你需要[启用 TKE 集群驱动](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#激活停用集群驱动)。启用集群驱动后，你可以开始配置 TKE 集群。 - -## 腾讯先决条件 - -:::caution - -部署到 TKE 会产生费用。 - -::: - -1. 参见[云访问管理](https://intl.cloud.tencent.com/document/product/598/10600)文档，确保用于创建 TKE 集群的账号具有适当的权限。 - -2. 创建[云 API 密钥 ID 和密钥](https://console.cloud.tencent.com/capi)。 - -3. 在要部署 Kubernetes 集群的区域中创建[私有网络和子网](https://intl.cloud.tencent.com/document/product/215/4927)。 - -4. 创建 [SSH 密钥对](https://intl.cloud.tencent.com/document/product/213/6092)。该密钥用于访问 Kubernetes 集群中的节点。 - -## Rancher 先决条件 - -你需要启用腾讯 TKE 集群驱动： - -1. 点击 **☰ > 集群管理**。 -1. 点击**驱动**。 -1. 在**集群驱动**选项卡中，转到 **Tencent TKE** 集群驱动并单击 **⋮ > 激活**。 - -集群驱动下载完成后，就可以在 Rancher 中创建腾讯 TKE 集群了。 - -## 创建 TKE 集群 - -1. 在**集群**页面，点击**创建**。 - -2. 选择 **Tencent TKE**。 - -3. 输入**集群名称**。 - -4. 使用**成员角色**为集群配置用户授权。点击**添加成员**添加可以访问集群的用户。使用**角色**下拉菜单为每个用户设置权限。 - -5. 为 TKE 集群配置**账号访问**。使用[先决条件](#腾讯先决条件)中获得的信息完成每个下拉列表和字段。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 区域 | 从下拉列表中选择构建集群的地理区域。 | - | 密文 ID | 输入从腾讯云控制台获取的密文 ID。 | - | 密文密钥 | 输入从腾讯云控制台获取的密文密钥。 | - -6. 然后，单击`下一步：配置集群`来配置 TKE 集群。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes 版本 | TKE 目前只支持 Kubernetes 1.10.5。 | - | 节点数 | 输入要为 Kubernetes 集群购买的 worker 节点数，最大值是 100。 | - | VPC | 选择在腾讯云控制台中创建的 VPC 名称。 | - | 容器网络 CIDR | 输入 Kubernetes 集群的 CIDR 范围。你可以在腾讯云控制台的 VPC 服务中查看该 CIDR 的可用范围。默认为 172.16.0.0/16。 | - - :::note - - 如果你在 `cluster.yml` 中编辑集群，而不是使用 Rancher UI，则集群配置参数必须嵌套在 `cluster.yml` 中的 `rancher_kubernetes_engine_config` 中。有关详细信息，请参阅 [Rancher 2.3.0+ 配置文件结构](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#rancher-中的配置文件结构)。 - - ::: - -7. 点击`下一步：选择实例类型`，然后选择将用于 TKE 集群的实例类型。 - - | 选项 | 描述 | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | 可用区 | 选择 VPC 区域的可用区。 | - | 子网 | 选择你在 VPC 中创建的子网。如果在所选可用区中没有该子网，请添加一个新子网。 | - | 实例类型 | 从下拉列表中选择要用于 TKE 集群的 VM 实例类型，默认为 S2.MEDIUM4（CPU 2；内存 4 GiB）。 | - -8. 点击`下一步：配置实例`，配置用于 TKE 集群的 VM 实例。 - - | 选项 | 描述 | - -------|------------ - | 操作系统 | 操作系统名称，目前支持 Centos7.2x86_64 或 ubuntu16.04.1 LTSx86_64。 | - | 安全组 | 安全组 ID，默认不绑定任何安全组。 | - | 根磁盘类型 | 系统盘类型。系统盘类型限制详见 [CVM 实例配置](https://cloud.tencent.com/document/product/213/11518)。 | - | 根磁盘大小 | 系统盘大小。Linux 系统调整范围为 20-50 GB，步长为 1。 | - | 数据盘类型 | 数据盘类型，默认为 SSD 云盘。 | - | 数据磁盘大小 | 数据盘大小（GB），步长为 10。 | - | 带宽类型 | 带宽收费类型，PayByTraffic 或 PayByHour。 | - | 带宽 | 公网带宽 (Mbps) | - | 密钥对 | 密钥 ID，关联后可以用来登录 VM 节点。 | - -9. 单击**创建**。 - -**结果**： - -你已创建集群，集群的状态是**配置中**。Rancher 已在你的集群中。 - -当集群状态变为 **Active** 后，你可访问集群。 - -**Active** 状态的集群会分配到两个项目： - -- `Default`：包含 `default` 命名空间 -- `System`：包含 `cattle-system`，`ingress-nginx`，`kube-public` 和 `kube-system` 命名空间。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/pages-for-subheaders/about-provisioning-drivers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/pages-for-subheaders/about-provisioning-drivers.md index d201eee3c65..03e6bb43a7f 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/pages-for-subheaders/about-provisioning-drivers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/pages-for-subheaders/about-provisioning-drivers.md @@ -23,12 +23,6 @@ Rancher 中有两种类型的驱动： * [Google GKE](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -还有几个托管的 Kubernetes 云提供商是默认禁用的，但也打包在 Rancher 中： - -* [Alibaba ACK](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ### 主机驱动 主机驱动用于配置主机，Rancher 使用这些主机启动和管理 Kubernetes 集群。主机驱动与 [Docker Machine 驱动](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md)相同。创建主机模板时可以显示的主机驱动，是由主机驱动的状态定义的。只有 `active` 主机驱动将显示为创建节点模板的选项。默认情况下，Rancher 与许多现有的 Docker Machine 驱动打包在一起，但你也可以创建自定义主机驱动并添加到 Rancher。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/pages-for-subheaders/set-up-clusters-from-hosted-kubernetes-providers.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/pages-for-subheaders/set-up-clusters-from-hosted-kubernetes-providers.md index d93fda6f3a6..77c2e405a1f 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/pages-for-subheaders/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/pages-for-subheaders/set-up-clusters-from-hosted-kubernetes-providers.md @@ -13,9 +13,6 @@ Rancher 支持以下 Kubernetes 提供商： - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## 托管 Kubernetes 提供商的身份验证 @@ -24,6 +21,3 @@ Rancher 支持以下 Kubernetes 提供商： - [创建 GKE 集群](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) - [创建 EKS 集群](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks.md) - [创建 AKS 集群](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -- [创建 ACK 集群](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -- [创建 TKE 集群](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) -- [创建 CCE 集群](../how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) diff --git a/sidebars.js b/sidebars.js index f38580109b8..9e8047f1396 100644 --- a/sidebars.js +++ b/sidebars.js @@ -462,9 +462,6 @@ const sidebars = { "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks", "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke", "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei", ], }, { diff --git a/versioned_docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/versioned_docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index 959fba86e28..e83ae0a7744 100644 --- a/versioned_docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/versioned_docs/version-2.10/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ By default, Rancher has activated several hosted Kubernetes cloud providers incl * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -There are several other hosted Kubernetes cloud providers that are disabled by default, but are packaged in Rancher: - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ### Node Drivers Node drivers are used to provision hosts, which Rancher uses to launch and manage Kubernetes clusters. A node driver is the same as a [Docker Machine driver](https://docs.docker.com/machine/drivers/). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. diff --git a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index 82cdde8861f..00000000000 --- a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Creating an Aliyun ACK Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Alibaba Cloud Kubernetes (ACK). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for ACK, but by default, this cluster driver is `inactive`. In order to launch ACK clusters, you will need to [enable the ACK cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning ACK clusters. - -## Prerequisites Outside of Rancher - -:::caution - -Deploying to ACK will incur charges. - -::: - -1. In Aliyun, activate the following services in their respective consoles. - - - [Container Service](https://cs.console.aliyun.com) - - [Resource Orchestration Service](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. Make sure that the account you will be using to create the ACK cluster has the appropriate permissions. Referring to the official Alibaba Cloud documentation about [Role authorization](https://www.alibabacloud.com/help/doc-detail/86483.htm) and [Use the Container Service console as a RAM user](https://www.alibabacloud.com/help/doc-detail/86484.htm) for details. - -3. In Alibaba Cloud, create an [access key](https://www.alibabacloud.com/help/doc-detail/53045.html). - -4. In Alibaba Cloud, create an [SSH key pair](https://www.alibabacloud.com/help/doc-detail/51793.html). This key is used to access nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Alibaba ACK cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Alibaba ACK** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Alibaba ACK clusters in Rancher. - -## Create an ACK Cluster - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, click **Create**. -1. Choose **Alibaba ACK**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Configure **Account Access** for the ACK cluster. Choose the geographical region in which to build your cluster, and input the access key that was created as part of the prerequisite steps. -1. Click **Next: Configure Cluster**, then choose cluster type, the version of Kubernetes and the availability zone. -1. If you choose **Kubernetes** as the cluster type, Click **Next: Configure Master Nodes**, then complete the **Master Nodes** form. -1. Click **Next: Configure Worker Nodes**, then complete the **Worker Nodes** form. -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index cbde0642b88..00000000000 --- a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -title: Creating a Huawei CCE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Huawei Cloud Container Engine (CCE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for CCE, but by default, this cluster driver is `inactive`. In order to launch CCE clusters, you will need to [enable the CCE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning CCE clusters. - -## Prerequisites in Huawei - -:::caution - -Deploying to CCE will incur charges. - -::: - -1. Find your project ID in Huawei CCE portal. See the CCE documentation on how to [manage your projects](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214). - -2. Create an [Access Key ID and Secret Access Key](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html). - -## Prerequisite in Rancher - -You will need to enable the Huawei CCE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Huawei CCE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Huawei CCE clusters in Rancher. - -## Limitations - -Huawei CCE service doesn't support the ability to create clusters with public access through their API. You are required to run Rancher in the same VPC as the CCE clusters that you want to provision. - -## Create the CCE Cluster - -1. From the **Clusters** page, click **Create**. -1. Click **Huawei CCE**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Enter **Project Id**, Access Key ID as **Access Key** and Secret Access Key **Secret Key**. Then Click **Next: Configure cluster**. Fill in the cluster configuration. For help filling out the form, refer to [Huawei CCE Configuration.](#huawei-cce-configuration) -1. Fill the following node configuration of the cluster. For help filling out the form, refer to [Node Configuration.](#node-configuration) -1. Click **Create** to create the CCE cluster. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -## Huawei CCE Configuration - -|Settings|Description| -|---|---| -| Cluster Type | Which type or node you want to include into the cluster, `VirtualMachine` or `BareMetal`. | -| Description | The description of the cluster. | -| Master Version | The Kubernetes version. | -| Management Scale Count | The max node count of the cluster. The options are 50, 200 and 1000. The larger of the scale count, the more the cost. | -| High Availability | Enable master node high availability. The cluster with high availability enabled will have more cost. | -| Container Network Mode | The network mode used in the cluster. `overlay_l2` and `vpc-router` is supported in `VirtualMachine` type and `underlay_ipvlan` is supported in `BareMetal` type | -| Container Network CIDR | Network CIDR for the cluster. | -| VPC Name | The VPC name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| Subnet Name | The Subnet name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| External Server | This option is reserved for the future we can enable CCE cluster public access via API. For now, it is always disabled. | -| Cluster Label | The labels for the cluster. | -| Highway Subnet | This option is only supported in `BareMetal` type. It requires you to select a VPC with high network speed for the bare metal machines. | - -:::note - -If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - -::: - -## Node Configuration - -|Settings|Description| -|---|---| -| Zone | The available zone at where the node(s) of the cluster is deployed. | -| Billing Mode | The bill mode for the cluster node(s). In `VirtualMachine` type, only `Pay-per-use` is supported. in `BareMetal`, you can choose `Pay-per-use` or `Yearly/Monthly`. | -| Validity Period | This option only shows in `Yearly/Monthly` bill mode. It means how long you want to pay for the cluster node(s). | -| Auto Renew | This option only shows in `Yearly/Monthly` bill mode. It means that the cluster node(s) will renew the `Yearly/Monthly` payment automatically or not. | -| Data Volume Type | Data volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Data Volume Size | Data volume size for the cluster node(s) | -| Root Volume Type | Root volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Root Volume Size | Root volume size for the cluster node(s) | -| Node Flavor | The node flavor of the cluster node(s). The flavor list in Rancher UI is fetched from Huawei Cloud. It includes all the supported node flavors. | -| Node Count | The node count of the cluster | -| Node Operating System | The operating system for the cluster node(s). Only `EulerOS 2.2` and `CentOS 7.4` are supported right now. | -| SSH Key Name | The ssh key for the cluster node(s) | -| EIP | The public IP options for the cluster node(s). `Disabled` means that the cluster node(s) are not going to bind a public IP. `Create EIP` means that the cluster node(s) will bind one or many newly created Eips after provisioned and more options will be shown in the UI to set the to-create EIP parameters. And `Select Existed EIP` means that the node(s) will bind to the EIPs you select. | -| EIP Count | This option will only be shown when `Create EIP` is selected. It means how many EIPs you want to create for the node(s). | -| EIP Type | This option will only be shown when `Create EIP` is selected. The options are `5_bgp` and `5_sbgp`. | -| EIP Share Type | This option will only be shown when `Create EIP` is selected. The only option is `PER`. | -| EIP Charge Mode | This option will only be shown when `Create EIP` is selected. The options are pay by `BandWidth` and pay by `Traffic`. | -| EIP Bandwidth Size | This option will only be shown when `Create EIP` is selected. The BandWidth of the EIPs. | -| Authentication Mode | It means enabling `RBAC` or also enabling `Authenticating Proxy`. If you select `Authenticating Proxy`, the certificate which is used for authenticating proxy will be also required. | -| Node Label | The labels for the cluster node(s). Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) | \ No newline at end of file diff --git a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index ea0cc4ff394..946906ae614 100644 --- a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher supports the following Kubernetes providers: - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## Hosted Kubernetes Provider Authentication @@ -28,6 +25,3 @@ When using Rancher to create a cluster hosted by a provider, you are prompted fo - [Creating a GKE Cluster](gke.md) - [Creating an EKS Cluster](eks.md) - [Creating an AKS Cluster](aks.md) -- [Creating an ACK Cluster](alibaba.md) -- [Creating a TKE Cluster](tencent.md) -- [Creating a CCE Cluster](huawei.md) diff --git a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 35cd4cc9b1c..00000000000 --- a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Creating a Tencent TKE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Tencent Kubernetes Engine (TKE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for TKE, but by default, this cluster driver is `inactive`. In order to launch TKE clusters, you will need to [enable the TKE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning TKE clusters. - -## Prerequisites in Tencent - -:::caution - -Deploying to TKE will incur charges. - -::: - -1. Make sure that the account you will be using to create the TKE cluster has the appropriate permissions by referring to the [Cloud Access Management](https://intl.cloud.tencent.com/document/product/598/10600) documentation for details. - -2. Create a [Cloud API Secret ID and Secret Key](https://console.cloud.tencent.com/capi). - -3. Create a [Private Network and Subnet](https://intl.cloud.tencent.com/document/product/215/4927) in the region that you want to deploy your Kubernetes cluster. - -4. Create a [SSH key pair](https://intl.cloud.tencent.com/document/product/213/6092). This key is used to access the nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Tencent TKE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Tencent TKE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Tencent TKE clusters in Rancher. - -## Create a TKE Cluster - -1. From the **Clusters** page, click **Create**. - -2. Choose **Tencent TKE**. - -3. Enter a **Cluster Name**. - -4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. - -5. Configure **Account Access** for the TKE cluster. Complete each drop-down and field using the information obtained in [Prerequisites](#prerequisites-in-tencent). - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Region | From the drop-down chooses the geographical region in which to build your cluster. | - | Secret ID | Enter the Secret ID that you obtained from the Tencent Cloud Console. | - | Secret Key | Enter the Secret key that you obtained from Tencent Cloud Console. | - -6. Click `Next: Configure Cluster` to set your TKE cluster configurations. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes Version | The TKE only supports Kubernetes version 1.10.5 now. | - | Node Count | Enter the amount of worker node you want to purchase for your Kubernetes cluster, up to 100. | - | VPC | Select the VPC name that you have created in the Tencent Cloud Console. | - | Container Network CIDR | Enter the CIDR range of your Kubernetes cluster, you may check the available range of the CIDR in the VPC service of the Tencent Cloud Console. Default to 172.16.0.0/16. | - - :::note - - If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that, cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure in Rancher v2.3.0+.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - - ::: - -7. Click `Next: Select Instance Type` to choose the instance type that will use for your TKE cluster. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Availability Zone | Choose the availability zone of the VPC region. | - | Subnet | Select the Subnet that you have created within the VPC, and add a new one if you don't have it in the chosen availability zone. | - | Instance Type | From the drop-down chooses the VM instance type that you want to use for the TKE cluster, default to S2.MEDIUM4 (CPU 2 Memory 4 GiB). | - -8. Click `Next: Configure Instance` to configure the VM instance that will use for your TKE cluster. - - Option | Description - -------|------------ - Operating System | The name of the operating system, currently supports Centos7.2x86_64 or ubuntu16.04.1 LTSx86_64 - Security Group | Security group ID, default does not bind any security groups. - Root Disk Type | System disk type. System disk type restrictions are detailed in the [CVM instance configuration](https://cloud.tencent.com/document/product/213/11518). - Root Disk Size | System disk size. Linux system adjustment range is 20 - 50G, step size is 1. - Data Disk Type | Data disk type, default value to the SSD cloud drive - Data Disk Size | Data disk size (GB), the step size is 10 - Band Width Type | Type of bandwidth, PayByTraffic or PayByHour - Band Width | Public network bandwidth (Mbps) - Key Pair | Key id, after associating the key can be used to logging to the VM node - -9. Click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/versioned_docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index 2295d1cf196..c6e4a3bb583 100644 --- a/versioned_docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/versioned_docs/version-2.11/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ By default, Rancher has activated several hosted Kubernetes cloud providers incl * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -There are several other hosted Kubernetes cloud providers that are disabled by default, but are packaged in Rancher: - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ### Node Drivers Node drivers are used to provision hosts, which Rancher uses to launch and manage Kubernetes clusters. A node driver is the same as a [Docker Machine driver](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. diff --git a/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index 82cdde8861f..00000000000 --- a/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Creating an Aliyun ACK Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Alibaba Cloud Kubernetes (ACK). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for ACK, but by default, this cluster driver is `inactive`. In order to launch ACK clusters, you will need to [enable the ACK cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning ACK clusters. - -## Prerequisites Outside of Rancher - -:::caution - -Deploying to ACK will incur charges. - -::: - -1. In Aliyun, activate the following services in their respective consoles. - - - [Container Service](https://cs.console.aliyun.com) - - [Resource Orchestration Service](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. Make sure that the account you will be using to create the ACK cluster has the appropriate permissions. Referring to the official Alibaba Cloud documentation about [Role authorization](https://www.alibabacloud.com/help/doc-detail/86483.htm) and [Use the Container Service console as a RAM user](https://www.alibabacloud.com/help/doc-detail/86484.htm) for details. - -3. In Alibaba Cloud, create an [access key](https://www.alibabacloud.com/help/doc-detail/53045.html). - -4. In Alibaba Cloud, create an [SSH key pair](https://www.alibabacloud.com/help/doc-detail/51793.html). This key is used to access nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Alibaba ACK cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Alibaba ACK** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Alibaba ACK clusters in Rancher. - -## Create an ACK Cluster - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, click **Create**. -1. Choose **Alibaba ACK**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Configure **Account Access** for the ACK cluster. Choose the geographical region in which to build your cluster, and input the access key that was created as part of the prerequisite steps. -1. Click **Next: Configure Cluster**, then choose cluster type, the version of Kubernetes and the availability zone. -1. If you choose **Kubernetes** as the cluster type, Click **Next: Configure Master Nodes**, then complete the **Master Nodes** form. -1. Click **Next: Configure Worker Nodes**, then complete the **Worker Nodes** form. -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index cbde0642b88..00000000000 --- a/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -title: Creating a Huawei CCE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Huawei Cloud Container Engine (CCE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for CCE, but by default, this cluster driver is `inactive`. In order to launch CCE clusters, you will need to [enable the CCE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning CCE clusters. - -## Prerequisites in Huawei - -:::caution - -Deploying to CCE will incur charges. - -::: - -1. Find your project ID in Huawei CCE portal. See the CCE documentation on how to [manage your projects](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214). - -2. Create an [Access Key ID and Secret Access Key](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html). - -## Prerequisite in Rancher - -You will need to enable the Huawei CCE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Huawei CCE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Huawei CCE clusters in Rancher. - -## Limitations - -Huawei CCE service doesn't support the ability to create clusters with public access through their API. You are required to run Rancher in the same VPC as the CCE clusters that you want to provision. - -## Create the CCE Cluster - -1. From the **Clusters** page, click **Create**. -1. Click **Huawei CCE**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Enter **Project Id**, Access Key ID as **Access Key** and Secret Access Key **Secret Key**. Then Click **Next: Configure cluster**. Fill in the cluster configuration. For help filling out the form, refer to [Huawei CCE Configuration.](#huawei-cce-configuration) -1. Fill the following node configuration of the cluster. For help filling out the form, refer to [Node Configuration.](#node-configuration) -1. Click **Create** to create the CCE cluster. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -## Huawei CCE Configuration - -|Settings|Description| -|---|---| -| Cluster Type | Which type or node you want to include into the cluster, `VirtualMachine` or `BareMetal`. | -| Description | The description of the cluster. | -| Master Version | The Kubernetes version. | -| Management Scale Count | The max node count of the cluster. The options are 50, 200 and 1000. The larger of the scale count, the more the cost. | -| High Availability | Enable master node high availability. The cluster with high availability enabled will have more cost. | -| Container Network Mode | The network mode used in the cluster. `overlay_l2` and `vpc-router` is supported in `VirtualMachine` type and `underlay_ipvlan` is supported in `BareMetal` type | -| Container Network CIDR | Network CIDR for the cluster. | -| VPC Name | The VPC name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| Subnet Name | The Subnet name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| External Server | This option is reserved for the future we can enable CCE cluster public access via API. For now, it is always disabled. | -| Cluster Label | The labels for the cluster. | -| Highway Subnet | This option is only supported in `BareMetal` type. It requires you to select a VPC with high network speed for the bare metal machines. | - -:::note - -If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - -::: - -## Node Configuration - -|Settings|Description| -|---|---| -| Zone | The available zone at where the node(s) of the cluster is deployed. | -| Billing Mode | The bill mode for the cluster node(s). In `VirtualMachine` type, only `Pay-per-use` is supported. in `BareMetal`, you can choose `Pay-per-use` or `Yearly/Monthly`. | -| Validity Period | This option only shows in `Yearly/Monthly` bill mode. It means how long you want to pay for the cluster node(s). | -| Auto Renew | This option only shows in `Yearly/Monthly` bill mode. It means that the cluster node(s) will renew the `Yearly/Monthly` payment automatically or not. | -| Data Volume Type | Data volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Data Volume Size | Data volume size for the cluster node(s) | -| Root Volume Type | Root volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Root Volume Size | Root volume size for the cluster node(s) | -| Node Flavor | The node flavor of the cluster node(s). The flavor list in Rancher UI is fetched from Huawei Cloud. It includes all the supported node flavors. | -| Node Count | The node count of the cluster | -| Node Operating System | The operating system for the cluster node(s). Only `EulerOS 2.2` and `CentOS 7.4` are supported right now. | -| SSH Key Name | The ssh key for the cluster node(s) | -| EIP | The public IP options for the cluster node(s). `Disabled` means that the cluster node(s) are not going to bind a public IP. `Create EIP` means that the cluster node(s) will bind one or many newly created Eips after provisioned and more options will be shown in the UI to set the to-create EIP parameters. And `Select Existed EIP` means that the node(s) will bind to the EIPs you select. | -| EIP Count | This option will only be shown when `Create EIP` is selected. It means how many EIPs you want to create for the node(s). | -| EIP Type | This option will only be shown when `Create EIP` is selected. The options are `5_bgp` and `5_sbgp`. | -| EIP Share Type | This option will only be shown when `Create EIP` is selected. The only option is `PER`. | -| EIP Charge Mode | This option will only be shown when `Create EIP` is selected. The options are pay by `BandWidth` and pay by `Traffic`. | -| EIP Bandwidth Size | This option will only be shown when `Create EIP` is selected. The BandWidth of the EIPs. | -| Authentication Mode | It means enabling `RBAC` or also enabling `Authenticating Proxy`. If you select `Authenticating Proxy`, the certificate which is used for authenticating proxy will be also required. | -| Node Label | The labels for the cluster node(s). Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) | \ No newline at end of file diff --git a/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index ea0cc4ff394..946906ae614 100644 --- a/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher supports the following Kubernetes providers: - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## Hosted Kubernetes Provider Authentication @@ -28,6 +25,3 @@ When using Rancher to create a cluster hosted by a provider, you are prompted fo - [Creating a GKE Cluster](gke.md) - [Creating an EKS Cluster](eks.md) - [Creating an AKS Cluster](aks.md) -- [Creating an ACK Cluster](alibaba.md) -- [Creating a TKE Cluster](tencent.md) -- [Creating a CCE Cluster](huawei.md) diff --git a/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 35cd4cc9b1c..00000000000 --- a/versioned_docs/version-2.11/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Creating a Tencent TKE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Tencent Kubernetes Engine (TKE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for TKE, but by default, this cluster driver is `inactive`. In order to launch TKE clusters, you will need to [enable the TKE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning TKE clusters. - -## Prerequisites in Tencent - -:::caution - -Deploying to TKE will incur charges. - -::: - -1. Make sure that the account you will be using to create the TKE cluster has the appropriate permissions by referring to the [Cloud Access Management](https://intl.cloud.tencent.com/document/product/598/10600) documentation for details. - -2. Create a [Cloud API Secret ID and Secret Key](https://console.cloud.tencent.com/capi). - -3. Create a [Private Network and Subnet](https://intl.cloud.tencent.com/document/product/215/4927) in the region that you want to deploy your Kubernetes cluster. - -4. Create a [SSH key pair](https://intl.cloud.tencent.com/document/product/213/6092). This key is used to access the nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Tencent TKE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Tencent TKE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Tencent TKE clusters in Rancher. - -## Create a TKE Cluster - -1. From the **Clusters** page, click **Create**. - -2. Choose **Tencent TKE**. - -3. Enter a **Cluster Name**. - -4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. - -5. Configure **Account Access** for the TKE cluster. Complete each drop-down and field using the information obtained in [Prerequisites](#prerequisites-in-tencent). - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Region | From the drop-down chooses the geographical region in which to build your cluster. | - | Secret ID | Enter the Secret ID that you obtained from the Tencent Cloud Console. | - | Secret Key | Enter the Secret key that you obtained from Tencent Cloud Console. | - -6. Click `Next: Configure Cluster` to set your TKE cluster configurations. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes Version | The TKE only supports Kubernetes version 1.10.5 now. | - | Node Count | Enter the amount of worker node you want to purchase for your Kubernetes cluster, up to 100. | - | VPC | Select the VPC name that you have created in the Tencent Cloud Console. | - | Container Network CIDR | Enter the CIDR range of your Kubernetes cluster, you may check the available range of the CIDR in the VPC service of the Tencent Cloud Console. Default to 172.16.0.0/16. | - - :::note - - If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that, cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure in Rancher v2.3.0+.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - - ::: - -7. Click `Next: Select Instance Type` to choose the instance type that will use for your TKE cluster. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Availability Zone | Choose the availability zone of the VPC region. | - | Subnet | Select the Subnet that you have created within the VPC, and add a new one if you don't have it in the chosen availability zone. | - | Instance Type | From the drop-down chooses the VM instance type that you want to use for the TKE cluster, default to S2.MEDIUM4 (CPU 2 Memory 4 GiB). | - -8. Click `Next: Configure Instance` to configure the VM instance that will use for your TKE cluster. - - Option | Description - -------|------------ - Operating System | The name of the operating system, currently supports Centos7.2x86_64 or ubuntu16.04.1 LTSx86_64 - Security Group | Security group ID, default does not bind any security groups. - Root Disk Type | System disk type. System disk type restrictions are detailed in the [CVM instance configuration](https://cloud.tencent.com/document/product/213/11518). - Root Disk Size | System disk size. Linux system adjustment range is 20 - 50G, step size is 1. - Data Disk Type | Data disk type, default value to the SSD cloud drive - Data Disk Size | Data disk size (GB), the step size is 10 - Band Width Type | Type of bandwidth, PayByTraffic or PayByHour - Band Width | Public network bandwidth (Mbps) - Key Pair | Key id, after associating the key can be used to logging to the VM node - -9. Click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/versioned_docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index 63b78e20f4c..6edd8965a06 100644 --- a/versioned_docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/versioned_docs/version-2.12/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ By default, Rancher has activated several hosted Kubernetes cloud providers incl * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -There are several other hosted Kubernetes cloud providers that are disabled by default, but are packaged in Rancher: - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ### Node Drivers Node drivers are used to provision hosts, which Rancher uses to launch and manage Kubernetes clusters. A node driver is the same as a [Docker Machine driver](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. diff --git a/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index 82cdde8861f..00000000000 --- a/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Creating an Aliyun ACK Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Alibaba Cloud Kubernetes (ACK). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for ACK, but by default, this cluster driver is `inactive`. In order to launch ACK clusters, you will need to [enable the ACK cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning ACK clusters. - -## Prerequisites Outside of Rancher - -:::caution - -Deploying to ACK will incur charges. - -::: - -1. In Aliyun, activate the following services in their respective consoles. - - - [Container Service](https://cs.console.aliyun.com) - - [Resource Orchestration Service](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. Make sure that the account you will be using to create the ACK cluster has the appropriate permissions. Referring to the official Alibaba Cloud documentation about [Role authorization](https://www.alibabacloud.com/help/doc-detail/86483.htm) and [Use the Container Service console as a RAM user](https://www.alibabacloud.com/help/doc-detail/86484.htm) for details. - -3. In Alibaba Cloud, create an [access key](https://www.alibabacloud.com/help/doc-detail/53045.html). - -4. In Alibaba Cloud, create an [SSH key pair](https://www.alibabacloud.com/help/doc-detail/51793.html). This key is used to access nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Alibaba ACK cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Alibaba ACK** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Alibaba ACK clusters in Rancher. - -## Create an ACK Cluster - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, click **Create**. -1. Choose **Alibaba ACK**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Configure **Account Access** for the ACK cluster. Choose the geographical region in which to build your cluster, and input the access key that was created as part of the prerequisite steps. -1. Click **Next: Configure Cluster**, then choose cluster type, the version of Kubernetes and the availability zone. -1. If you choose **Kubernetes** as the cluster type, Click **Next: Configure Master Nodes**, then complete the **Master Nodes** form. -1. Click **Next: Configure Worker Nodes**, then complete the **Worker Nodes** form. -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index cbde0642b88..00000000000 --- a/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -title: Creating a Huawei CCE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Huawei Cloud Container Engine (CCE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for CCE, but by default, this cluster driver is `inactive`. In order to launch CCE clusters, you will need to [enable the CCE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning CCE clusters. - -## Prerequisites in Huawei - -:::caution - -Deploying to CCE will incur charges. - -::: - -1. Find your project ID in Huawei CCE portal. See the CCE documentation on how to [manage your projects](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214). - -2. Create an [Access Key ID and Secret Access Key](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html). - -## Prerequisite in Rancher - -You will need to enable the Huawei CCE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Huawei CCE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Huawei CCE clusters in Rancher. - -## Limitations - -Huawei CCE service doesn't support the ability to create clusters with public access through their API. You are required to run Rancher in the same VPC as the CCE clusters that you want to provision. - -## Create the CCE Cluster - -1. From the **Clusters** page, click **Create**. -1. Click **Huawei CCE**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Enter **Project Id**, Access Key ID as **Access Key** and Secret Access Key **Secret Key**. Then Click **Next: Configure cluster**. Fill in the cluster configuration. For help filling out the form, refer to [Huawei CCE Configuration.](#huawei-cce-configuration) -1. Fill the following node configuration of the cluster. For help filling out the form, refer to [Node Configuration.](#node-configuration) -1. Click **Create** to create the CCE cluster. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -## Huawei CCE Configuration - -|Settings|Description| -|---|---| -| Cluster Type | Which type or node you want to include into the cluster, `VirtualMachine` or `BareMetal`. | -| Description | The description of the cluster. | -| Master Version | The Kubernetes version. | -| Management Scale Count | The max node count of the cluster. The options are 50, 200 and 1000. The larger of the scale count, the more the cost. | -| High Availability | Enable master node high availability. The cluster with high availability enabled will have more cost. | -| Container Network Mode | The network mode used in the cluster. `overlay_l2` and `vpc-router` is supported in `VirtualMachine` type and `underlay_ipvlan` is supported in `BareMetal` type | -| Container Network CIDR | Network CIDR for the cluster. | -| VPC Name | The VPC name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| Subnet Name | The Subnet name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| External Server | This option is reserved for the future we can enable CCE cluster public access via API. For now, it is always disabled. | -| Cluster Label | The labels for the cluster. | -| Highway Subnet | This option is only supported in `BareMetal` type. It requires you to select a VPC with high network speed for the bare metal machines. | - -:::note - -If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - -::: - -## Node Configuration - -|Settings|Description| -|---|---| -| Zone | The available zone at where the node(s) of the cluster is deployed. | -| Billing Mode | The bill mode for the cluster node(s). In `VirtualMachine` type, only `Pay-per-use` is supported. in `BareMetal`, you can choose `Pay-per-use` or `Yearly/Monthly`. | -| Validity Period | This option only shows in `Yearly/Monthly` bill mode. It means how long you want to pay for the cluster node(s). | -| Auto Renew | This option only shows in `Yearly/Monthly` bill mode. It means that the cluster node(s) will renew the `Yearly/Monthly` payment automatically or not. | -| Data Volume Type | Data volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Data Volume Size | Data volume size for the cluster node(s) | -| Root Volume Type | Root volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Root Volume Size | Root volume size for the cluster node(s) | -| Node Flavor | The node flavor of the cluster node(s). The flavor list in Rancher UI is fetched from Huawei Cloud. It includes all the supported node flavors. | -| Node Count | The node count of the cluster | -| Node Operating System | The operating system for the cluster node(s). Only `EulerOS 2.2` and `CentOS 7.4` are supported right now. | -| SSH Key Name | The ssh key for the cluster node(s) | -| EIP | The public IP options for the cluster node(s). `Disabled` means that the cluster node(s) are not going to bind a public IP. `Create EIP` means that the cluster node(s) will bind one or many newly created Eips after provisioned and more options will be shown in the UI to set the to-create EIP parameters. And `Select Existed EIP` means that the node(s) will bind to the EIPs you select. | -| EIP Count | This option will only be shown when `Create EIP` is selected. It means how many EIPs you want to create for the node(s). | -| EIP Type | This option will only be shown when `Create EIP` is selected. The options are `5_bgp` and `5_sbgp`. | -| EIP Share Type | This option will only be shown when `Create EIP` is selected. The only option is `PER`. | -| EIP Charge Mode | This option will only be shown when `Create EIP` is selected. The options are pay by `BandWidth` and pay by `Traffic`. | -| EIP Bandwidth Size | This option will only be shown when `Create EIP` is selected. The BandWidth of the EIPs. | -| Authentication Mode | It means enabling `RBAC` or also enabling `Authenticating Proxy`. If you select `Authenticating Proxy`, the certificate which is used for authenticating proxy will be also required. | -| Node Label | The labels for the cluster node(s). Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) | \ No newline at end of file diff --git a/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index ea0cc4ff394..946906ae614 100644 --- a/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher supports the following Kubernetes providers: - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## Hosted Kubernetes Provider Authentication @@ -28,6 +25,3 @@ When using Rancher to create a cluster hosted by a provider, you are prompted fo - [Creating a GKE Cluster](gke.md) - [Creating an EKS Cluster](eks.md) - [Creating an AKS Cluster](aks.md) -- [Creating an ACK Cluster](alibaba.md) -- [Creating a TKE Cluster](tencent.md) -- [Creating a CCE Cluster](huawei.md) diff --git a/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 35cd4cc9b1c..00000000000 --- a/versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Creating a Tencent TKE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Tencent Kubernetes Engine (TKE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for TKE, but by default, this cluster driver is `inactive`. In order to launch TKE clusters, you will need to [enable the TKE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning TKE clusters. - -## Prerequisites in Tencent - -:::caution - -Deploying to TKE will incur charges. - -::: - -1. Make sure that the account you will be using to create the TKE cluster has the appropriate permissions by referring to the [Cloud Access Management](https://intl.cloud.tencent.com/document/product/598/10600) documentation for details. - -2. Create a [Cloud API Secret ID and Secret Key](https://console.cloud.tencent.com/capi). - -3. Create a [Private Network and Subnet](https://intl.cloud.tencent.com/document/product/215/4927) in the region that you want to deploy your Kubernetes cluster. - -4. Create a [SSH key pair](https://intl.cloud.tencent.com/document/product/213/6092). This key is used to access the nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Tencent TKE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Tencent TKE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Tencent TKE clusters in Rancher. - -## Create a TKE Cluster - -1. From the **Clusters** page, click **Create**. - -2. Choose **Tencent TKE**. - -3. Enter a **Cluster Name**. - -4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. - -5. Configure **Account Access** for the TKE cluster. Complete each drop-down and field using the information obtained in [Prerequisites](#prerequisites-in-tencent). - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Region | From the drop-down chooses the geographical region in which to build your cluster. | - | Secret ID | Enter the Secret ID that you obtained from the Tencent Cloud Console. | - | Secret Key | Enter the Secret key that you obtained from Tencent Cloud Console. | - -6. Click `Next: Configure Cluster` to set your TKE cluster configurations. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes Version | The TKE only supports Kubernetes version 1.10.5 now. | - | Node Count | Enter the amount of worker node you want to purchase for your Kubernetes cluster, up to 100. | - | VPC | Select the VPC name that you have created in the Tencent Cloud Console. | - | Container Network CIDR | Enter the CIDR range of your Kubernetes cluster, you may check the available range of the CIDR in the VPC service of the Tencent Cloud Console. Default to 172.16.0.0/16. | - - :::note - - If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that, cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure in Rancher v2.3.0+.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - - ::: - -7. Click `Next: Select Instance Type` to choose the instance type that will use for your TKE cluster. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Availability Zone | Choose the availability zone of the VPC region. | - | Subnet | Select the Subnet that you have created within the VPC, and add a new one if you don't have it in the chosen availability zone. | - | Instance Type | From the drop-down chooses the VM instance type that you want to use for the TKE cluster, default to S2.MEDIUM4 (CPU 2 Memory 4 GiB). | - -8. Click `Next: Configure Instance` to configure the VM instance that will use for your TKE cluster. - - Option | Description - -------|------------ - Operating System | The name of the operating system, currently supports Centos7.2x86_64 or ubuntu16.04.1 LTSx86_64 - Security Group | Security group ID, default does not bind any security groups. - Root Disk Type | System disk type. System disk type restrictions are detailed in the [CVM instance configuration](https://cloud.tencent.com/document/product/213/11518). - Root Disk Size | System disk size. Linux system adjustment range is 20 - 50G, step size is 1. - Data Disk Type | Data disk type, default value to the SSD cloud drive - Data Disk Size | Data disk size (GB), the step size is 10 - Band Width Type | Type of bandwidth, PayByTraffic or PayByHour - Band Width | Public network bandwidth (Mbps) - Key Pair | Key id, after associating the key can be used to logging to the VM node - -9. Click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index 2295d1cf196..c6e4a3bb583 100644 --- a/versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/versioned_docs/version-2.8/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ By default, Rancher has activated several hosted Kubernetes cloud providers incl * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -There are several other hosted Kubernetes cloud providers that are disabled by default, but are packaged in Rancher: - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ### Node Drivers Node drivers are used to provision hosts, which Rancher uses to launch and manage Kubernetes clusters. A node driver is the same as a [Docker Machine driver](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. diff --git a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index 82cdde8861f..00000000000 --- a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Creating an Aliyun ACK Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Alibaba Cloud Kubernetes (ACK). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for ACK, but by default, this cluster driver is `inactive`. In order to launch ACK clusters, you will need to [enable the ACK cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning ACK clusters. - -## Prerequisites Outside of Rancher - -:::caution - -Deploying to ACK will incur charges. - -::: - -1. In Aliyun, activate the following services in their respective consoles. - - - [Container Service](https://cs.console.aliyun.com) - - [Resource Orchestration Service](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. Make sure that the account you will be using to create the ACK cluster has the appropriate permissions. Referring to the official Alibaba Cloud documentation about [Role authorization](https://www.alibabacloud.com/help/doc-detail/86483.htm) and [Use the Container Service console as a RAM user](https://www.alibabacloud.com/help/doc-detail/86484.htm) for details. - -3. In Alibaba Cloud, create an [access key](https://www.alibabacloud.com/help/doc-detail/53045.html). - -4. In Alibaba Cloud, create an [SSH key pair](https://www.alibabacloud.com/help/doc-detail/51793.html). This key is used to access nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Alibaba ACK cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Alibaba ACK** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Alibaba ACK clusters in Rancher. - -## Create an ACK Cluster - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, click **Create**. -1. Choose **Alibaba ACK**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Configure **Account Access** for the ACK cluster. Choose the geographical region in which to build your cluster, and input the access key that was created as part of the prerequisite steps. -1. Click **Next: Configure Cluster**, then choose cluster type, the version of Kubernetes and the availability zone. -1. If you choose **Kubernetes** as the cluster type, Click **Next: Configure Master Nodes**, then complete the **Master Nodes** form. -1. Click **Next: Configure Worker Nodes**, then complete the **Worker Nodes** form. -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index cbde0642b88..00000000000 --- a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -title: Creating a Huawei CCE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Huawei Cloud Container Engine (CCE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for CCE, but by default, this cluster driver is `inactive`. In order to launch CCE clusters, you will need to [enable the CCE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning CCE clusters. - -## Prerequisites in Huawei - -:::caution - -Deploying to CCE will incur charges. - -::: - -1. Find your project ID in Huawei CCE portal. See the CCE documentation on how to [manage your projects](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214). - -2. Create an [Access Key ID and Secret Access Key](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html). - -## Prerequisite in Rancher - -You will need to enable the Huawei CCE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Huawei CCE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Huawei CCE clusters in Rancher. - -## Limitations - -Huawei CCE service doesn't support the ability to create clusters with public access through their API. You are required to run Rancher in the same VPC as the CCE clusters that you want to provision. - -## Create the CCE Cluster - -1. From the **Clusters** page, click **Create**. -1. Click **Huawei CCE**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Enter **Project Id**, Access Key ID as **Access Key** and Secret Access Key **Secret Key**. Then Click **Next: Configure cluster**. Fill in the cluster configuration. For help filling out the form, refer to [Huawei CCE Configuration.](#huawei-cce-configuration) -1. Fill the following node configuration of the cluster. For help filling out the form, refer to [Node Configuration.](#node-configuration) -1. Click **Create** to create the CCE cluster. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -## Huawei CCE Configuration - -|Settings|Description| -|---|---| -| Cluster Type | Which type or node you want to include into the cluster, `VirtualMachine` or `BareMetal`. | -| Description | The description of the cluster. | -| Master Version | The Kubernetes version. | -| Management Scale Count | The max node count of the cluster. The options are 50, 200 and 1000. The larger of the scale count, the more the cost. | -| High Availability | Enable master node high availability. The cluster with high availability enabled will have more cost. | -| Container Network Mode | The network mode used in the cluster. `overlay_l2` and `vpc-router` is supported in `VirtualMachine` type and `underlay_ipvlan` is supported in `BareMetal` type | -| Container Network CIDR | Network CIDR for the cluster. | -| VPC Name | The VPC name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| Subnet Name | The Subnet name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| External Server | This option is reserved for the future we can enable CCE cluster public access via API. For now, it is always disabled. | -| Cluster Label | The labels for the cluster. | -| Highway Subnet | This option is only supported in `BareMetal` type. It requires you to select a VPC with high network speed for the bare metal machines. | - -:::note - -If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - -::: - -## Node Configuration - -|Settings|Description| -|---|---| -| Zone | The available zone at where the node(s) of the cluster is deployed. | -| Billing Mode | The bill mode for the cluster node(s). In `VirtualMachine` type, only `Pay-per-use` is supported. in `BareMetal`, you can choose `Pay-per-use` or `Yearly/Monthly`. | -| Validity Period | This option only shows in `Yearly/Monthly` bill mode. It means how long you want to pay for the cluster node(s). | -| Auto Renew | This option only shows in `Yearly/Monthly` bill mode. It means that the cluster node(s) will renew the `Yearly/Monthly` payment automatically or not. | -| Data Volume Type | Data volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Data Volume Size | Data volume size for the cluster node(s) | -| Root Volume Type | Root volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Root Volume Size | Root volume size for the cluster node(s) | -| Node Flavor | The node flavor of the cluster node(s). The flavor list in Rancher UI is fetched from Huawei Cloud. It includes all the supported node flavors. | -| Node Count | The node count of the cluster | -| Node Operating System | The operating system for the cluster node(s). Only `EulerOS 2.2` and `CentOS 7.4` are supported right now. | -| SSH Key Name | The ssh key for the cluster node(s) | -| EIP | The public IP options for the cluster node(s). `Disabled` means that the cluster node(s) are not going to bind a public IP. `Create EIP` means that the cluster node(s) will bind one or many newly created Eips after provisioned and more options will be shown in the UI to set the to-create EIP parameters. And `Select Existed EIP` means that the node(s) will bind to the EIPs you select. | -| EIP Count | This option will only be shown when `Create EIP` is selected. It means how many EIPs you want to create for the node(s). | -| EIP Type | This option will only be shown when `Create EIP` is selected. The options are `5_bgp` and `5_sbgp`. | -| EIP Share Type | This option will only be shown when `Create EIP` is selected. The only option is `PER`. | -| EIP Charge Mode | This option will only be shown when `Create EIP` is selected. The options are pay by `BandWidth` and pay by `Traffic`. | -| EIP Bandwidth Size | This option will only be shown when `Create EIP` is selected. The BandWidth of the EIPs. | -| Authentication Mode | It means enabling `RBAC` or also enabling `Authenticating Proxy`. If you select `Authenticating Proxy`, the certificate which is used for authenticating proxy will be also required. | -| Node Label | The labels for the cluster node(s). Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) | \ No newline at end of file diff --git a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index ea0cc4ff394..946906ae614 100644 --- a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher supports the following Kubernetes providers: - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## Hosted Kubernetes Provider Authentication @@ -28,6 +25,3 @@ When using Rancher to create a cluster hosted by a provider, you are prompted fo - [Creating a GKE Cluster](gke.md) - [Creating an EKS Cluster](eks.md) - [Creating an AKS Cluster](aks.md) -- [Creating an ACK Cluster](alibaba.md) -- [Creating a TKE Cluster](tencent.md) -- [Creating a CCE Cluster](huawei.md) diff --git a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 35cd4cc9b1c..00000000000 --- a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Creating a Tencent TKE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Tencent Kubernetes Engine (TKE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for TKE, but by default, this cluster driver is `inactive`. In order to launch TKE clusters, you will need to [enable the TKE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning TKE clusters. - -## Prerequisites in Tencent - -:::caution - -Deploying to TKE will incur charges. - -::: - -1. Make sure that the account you will be using to create the TKE cluster has the appropriate permissions by referring to the [Cloud Access Management](https://intl.cloud.tencent.com/document/product/598/10600) documentation for details. - -2. Create a [Cloud API Secret ID and Secret Key](https://console.cloud.tencent.com/capi). - -3. Create a [Private Network and Subnet](https://intl.cloud.tencent.com/document/product/215/4927) in the region that you want to deploy your Kubernetes cluster. - -4. Create a [SSH key pair](https://intl.cloud.tencent.com/document/product/213/6092). This key is used to access the nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Tencent TKE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Tencent TKE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Tencent TKE clusters in Rancher. - -## Create a TKE Cluster - -1. From the **Clusters** page, click **Create**. - -2. Choose **Tencent TKE**. - -3. Enter a **Cluster Name**. - -4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. - -5. Configure **Account Access** for the TKE cluster. Complete each drop-down and field using the information obtained in [Prerequisites](#prerequisites-in-tencent). - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Region | From the drop-down chooses the geographical region in which to build your cluster. | - | Secret ID | Enter the Secret ID that you obtained from the Tencent Cloud Console. | - | Secret Key | Enter the Secret key that you obtained from Tencent Cloud Console. | - -6. Click `Next: Configure Cluster` to set your TKE cluster configurations. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes Version | The TKE only supports Kubernetes version 1.10.5 now. | - | Node Count | Enter the amount of worker node you want to purchase for your Kubernetes cluster, up to 100. | - | VPC | Select the VPC name that you have created in the Tencent Cloud Console. | - | Container Network CIDR | Enter the CIDR range of your Kubernetes cluster, you may check the available range of the CIDR in the VPC service of the Tencent Cloud Console. Default to 172.16.0.0/16. | - - :::note - - If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that, cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure in Rancher v2.3.0+.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - - ::: - -7. Click `Next: Select Instance Type` to choose the instance type that will use for your TKE cluster. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Availability Zone | Choose the availability zone of the VPC region. | - | Subnet | Select the Subnet that you have created within the VPC, and add a new one if you don't have it in the chosen availability zone. | - | Instance Type | From the drop-down chooses the VM instance type that you want to use for the TKE cluster, default to S2.MEDIUM4 (CPU 2 Memory 4 GiB). | - -8. Click `Next: Configure Instance` to configure the VM instance that will use for your TKE cluster. - - Option | Description - -------|------------ - Operating System | The name of the operating system, currently supports Centos7.2x86_64 or ubuntu16.04.1 LTSx86_64 - Security Group | Security group ID, default does not bind any security groups. - Root Disk Type | System disk type. System disk type restrictions are detailed in the [CVM instance configuration](https://cloud.tencent.com/document/product/213/11518). - Root Disk Size | System disk size. Linux system adjustment range is 20 - 50G, step size is 1. - Data Disk Type | Data disk type, default value to the SSD cloud drive - Data Disk Size | Data disk size (GB), the step size is 10 - Band Width Type | Type of bandwidth, PayByTraffic or PayByHour - Band Width | Public network bandwidth (Mbps) - Key Pair | Key id, after associating the key can be used to logging to the VM node - -9. Click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md b/versioned_docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md index 2295d1cf196..c6e4a3bb583 100644 --- a/versioned_docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md +++ b/versioned_docs/version-2.9/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/about-provisioning-drivers.md @@ -27,12 +27,6 @@ By default, Rancher has activated several hosted Kubernetes cloud providers incl * [Google GKE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md) * [Azure AKS](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks.md) -There are several other hosted Kubernetes cloud providers that are disabled by default, but are packaged in Rancher: - -* [Alibaba ACK](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md) -* [Huawei CCE](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md) -* [Tencent](../../kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md) - ### Node Drivers Node drivers are used to provision hosts, which Rancher uses to launch and manage Kubernetes clusters. A node driver is the same as a [Docker Machine driver](https://github.com/docker/docs/blob/vnext-engine/machine/drivers/index.md). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. diff --git a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md b/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md deleted file mode 100644 index 82cdde8861f..00000000000 --- a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Creating an Aliyun ACK Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Alibaba Cloud Kubernetes (ACK). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for ACK, but by default, this cluster driver is `inactive`. In order to launch ACK clusters, you will need to [enable the ACK cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning ACK clusters. - -## Prerequisites Outside of Rancher - -:::caution - -Deploying to ACK will incur charges. - -::: - -1. In Aliyun, activate the following services in their respective consoles. - - - [Container Service](https://cs.console.aliyun.com) - - [Resource Orchestration Service](https://ros.console.aliyun.com) - - [RAM](https://ram.console.aliyun.com) - -2. Make sure that the account you will be using to create the ACK cluster has the appropriate permissions. Referring to the official Alibaba Cloud documentation about [Role authorization](https://www.alibabacloud.com/help/doc-detail/86483.htm) and [Use the Container Service console as a RAM user](https://www.alibabacloud.com/help/doc-detail/86484.htm) for details. - -3. In Alibaba Cloud, create an [access key](https://www.alibabacloud.com/help/doc-detail/53045.html). - -4. In Alibaba Cloud, create an [SSH key pair](https://www.alibabacloud.com/help/doc-detail/51793.html). This key is used to access nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Alibaba ACK cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Alibaba ACK** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Alibaba ACK clusters in Rancher. - -## Create an ACK Cluster - -1. Click **☰ > Cluster Management**. -1. From the **Clusters** page, click **Create**. -1. Choose **Alibaba ACK**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Configure **Account Access** for the ACK cluster. Choose the geographical region in which to build your cluster, and input the access key that was created as part of the prerequisite steps. -1. Click **Next: Configure Cluster**, then choose cluster type, the version of Kubernetes and the availability zone. -1. If you choose **Kubernetes** as the cluster type, Click **Next: Configure Master Nodes**, then complete the **Master Nodes** form. -1. Click **Next: Configure Worker Nodes**, then complete the **Worker Nodes** form. -1. Review your options to confirm they're correct. Then click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md b/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md deleted file mode 100644 index cbde0642b88..00000000000 --- a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei.md +++ /dev/null @@ -1,104 +0,0 @@ ---- -title: Creating a Huawei CCE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Huawei Cloud Container Engine (CCE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for CCE, but by default, this cluster driver is `inactive`. In order to launch CCE clusters, you will need to [enable the CCE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning CCE clusters. - -## Prerequisites in Huawei - -:::caution - -Deploying to CCE will incur charges. - -::: - -1. Find your project ID in Huawei CCE portal. See the CCE documentation on how to [manage your projects](https://doc.hcs.huawei.com/api/cce/cce_02_0341.html#cce_02_0341__section17571944123214). - -2. Create an [Access Key ID and Secret Access Key](https://support.huaweicloud.com/en-us/usermanual-iam/en-us_topic_0079477318.html). - -## Prerequisite in Rancher - -You will need to enable the Huawei CCE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Huawei CCE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Huawei CCE clusters in Rancher. - -## Limitations - -Huawei CCE service doesn't support the ability to create clusters with public access through their API. You are required to run Rancher in the same VPC as the CCE clusters that you want to provision. - -## Create the CCE Cluster - -1. From the **Clusters** page, click **Create**. -1. Click **Huawei CCE**. -1. Enter a **Cluster Name**. -1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. -1. Enter **Project Id**, Access Key ID as **Access Key** and Secret Access Key **Secret Key**. Then Click **Next: Configure cluster**. Fill in the cluster configuration. For help filling out the form, refer to [Huawei CCE Configuration.](#huawei-cce-configuration) -1. Fill the following node configuration of the cluster. For help filling out the form, refer to [Node Configuration.](#node-configuration) -1. Click **Create** to create the CCE cluster. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces - -## Huawei CCE Configuration - -|Settings|Description| -|---|---| -| Cluster Type | Which type or node you want to include into the cluster, `VirtualMachine` or `BareMetal`. | -| Description | The description of the cluster. | -| Master Version | The Kubernetes version. | -| Management Scale Count | The max node count of the cluster. The options are 50, 200 and 1000. The larger of the scale count, the more the cost. | -| High Availability | Enable master node high availability. The cluster with high availability enabled will have more cost. | -| Container Network Mode | The network mode used in the cluster. `overlay_l2` and `vpc-router` is supported in `VirtualMachine` type and `underlay_ipvlan` is supported in `BareMetal` type | -| Container Network CIDR | Network CIDR for the cluster. | -| VPC Name | The VPC name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| Subnet Name | The Subnet name which the cluster is going to deploy into. Rancher will create one if it is blank. | -| External Server | This option is reserved for the future we can enable CCE cluster public access via API. For now, it is always disabled. | -| Cluster Label | The labels for the cluster. | -| Highway Subnet | This option is only supported in `BareMetal` type. It requires you to select a VPC with high network speed for the bare metal machines. | - -:::note - -If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - -::: - -## Node Configuration - -|Settings|Description| -|---|---| -| Zone | The available zone at where the node(s) of the cluster is deployed. | -| Billing Mode | The bill mode for the cluster node(s). In `VirtualMachine` type, only `Pay-per-use` is supported. in `BareMetal`, you can choose `Pay-per-use` or `Yearly/Monthly`. | -| Validity Period | This option only shows in `Yearly/Monthly` bill mode. It means how long you want to pay for the cluster node(s). | -| Auto Renew | This option only shows in `Yearly/Monthly` bill mode. It means that the cluster node(s) will renew the `Yearly/Monthly` payment automatically or not. | -| Data Volume Type | Data volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Data Volume Size | Data volume size for the cluster node(s) | -| Root Volume Type | Root volume type for the cluster node(s). `SATA`, `SSD` or `SAS` for this option. | -| Root Volume Size | Root volume size for the cluster node(s) | -| Node Flavor | The node flavor of the cluster node(s). The flavor list in Rancher UI is fetched from Huawei Cloud. It includes all the supported node flavors. | -| Node Count | The node count of the cluster | -| Node Operating System | The operating system for the cluster node(s). Only `EulerOS 2.2` and `CentOS 7.4` are supported right now. | -| SSH Key Name | The ssh key for the cluster node(s) | -| EIP | The public IP options for the cluster node(s). `Disabled` means that the cluster node(s) are not going to bind a public IP. `Create EIP` means that the cluster node(s) will bind one or many newly created Eips after provisioned and more options will be shown in the UI to set the to-create EIP parameters. And `Select Existed EIP` means that the node(s) will bind to the EIPs you select. | -| EIP Count | This option will only be shown when `Create EIP` is selected. It means how many EIPs you want to create for the node(s). | -| EIP Type | This option will only be shown when `Create EIP` is selected. The options are `5_bgp` and `5_sbgp`. | -| EIP Share Type | This option will only be shown when `Create EIP` is selected. The only option is `PER`. | -| EIP Charge Mode | This option will only be shown when `Create EIP` is selected. The options are pay by `BandWidth` and pay by `Traffic`. | -| EIP Bandwidth Size | This option will only be shown when `Create EIP` is selected. The BandWidth of the EIPs. | -| Authentication Mode | It means enabling `RBAC` or also enabling `Authenticating Proxy`. If you select `Authenticating Proxy`, the certificate which is used for authenticating proxy will be also required. | -| Node Label | The labels for the cluster node(s). Invalid labels can prevent upgrades or can prevent Rancher from starting. For details on label syntax requirements, see the [Kubernetes documentation.](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) | \ No newline at end of file diff --git a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md b/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md index ea0cc4ff394..946906ae614 100644 --- a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md +++ b/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/set-up-clusters-from-hosted-kubernetes-providers.md @@ -17,9 +17,6 @@ Rancher supports the following Kubernetes providers: - [Google GKE (Google Kubernetes Engine)](https://cloud.google.com/kubernetes-engine/) - [Amazon EKS (Amazon Elastic Container Service for Kubernetes)](https://aws.amazon.com/eks/) - [Microsoft AKS (Azure Kubernetes Service)](https://azure.microsoft.com/en-us/services/kubernetes-service/) -- [Alibaba ACK (Alibaba Cloud Container Service for Kubernetes)](https://www.alibabacloud.com/product/kubernetes) -- [Tencent TKE (Tencent Kubernetes Engine)](https://intl.cloud.tencent.com/product/tke) -- [Huawei CCE (Huawei Cloud Container Engine)](https://www.huaweicloud.com/en-us/product/cce.html) ## Hosted Kubernetes Provider Authentication @@ -28,6 +25,3 @@ When using Rancher to create a cluster hosted by a provider, you are prompted fo - [Creating a GKE Cluster](gke.md) - [Creating an EKS Cluster](eks.md) - [Creating an AKS Cluster](aks.md) -- [Creating an ACK Cluster](alibaba.md) -- [Creating a TKE Cluster](tencent.md) -- [Creating a CCE Cluster](huawei.md) diff --git a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md b/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md deleted file mode 100644 index 35cd4cc9b1c..00000000000 --- a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -title: Creating a Tencent TKE Cluster ---- - - - - - -You can use Rancher to create a cluster hosted in Tencent Kubernetes Engine (TKE). Rancher has already implemented and packaged the [cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md) for TKE, but by default, this cluster driver is `inactive`. In order to launch TKE clusters, you will need to [enable the TKE cluster driver](../../authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-cluster-drivers.md#activatingdeactivating-cluster-drivers). After enabling the cluster driver, you can start provisioning TKE clusters. - -## Prerequisites in Tencent - -:::caution - -Deploying to TKE will incur charges. - -::: - -1. Make sure that the account you will be using to create the TKE cluster has the appropriate permissions by referring to the [Cloud Access Management](https://intl.cloud.tencent.com/document/product/598/10600) documentation for details. - -2. Create a [Cloud API Secret ID and Secret Key](https://console.cloud.tencent.com/capi). - -3. Create a [Private Network and Subnet](https://intl.cloud.tencent.com/document/product/215/4927) in the region that you want to deploy your Kubernetes cluster. - -4. Create a [SSH key pair](https://intl.cloud.tencent.com/document/product/213/6092). This key is used to access the nodes in the Kubernetes cluster. - -## Prerequisite in Rancher - -You will need to enable the Tencent TKE cluster driver: - -1. Click **☰ > Cluster Management**. -1. Click **Drivers**. -1. In the **Cluster Drivers** tab, go to the **Tencent TKE** cluster driver and click **⋮ > Activate**. - -When the cluster driver is finished downloading, you will be able to create Tencent TKE clusters in Rancher. - -## Create a TKE Cluster - -1. From the **Clusters** page, click **Create**. - -2. Choose **Tencent TKE**. - -3. Enter a **Cluster Name**. - -4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user. - -5. Configure **Account Access** for the TKE cluster. Complete each drop-down and field using the information obtained in [Prerequisites](#prerequisites-in-tencent). - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Region | From the drop-down chooses the geographical region in which to build your cluster. | - | Secret ID | Enter the Secret ID that you obtained from the Tencent Cloud Console. | - | Secret Key | Enter the Secret key that you obtained from Tencent Cloud Console. | - -6. Click `Next: Configure Cluster` to set your TKE cluster configurations. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Kubernetes Version | The TKE only supports Kubernetes version 1.10.5 now. | - | Node Count | Enter the amount of worker node you want to purchase for your Kubernetes cluster, up to 100. | - | VPC | Select the VPC name that you have created in the Tencent Cloud Console. | - | Container Network CIDR | Enter the CIDR range of your Kubernetes cluster, you may check the available range of the CIDR in the VPC service of the Tencent Cloud Console. Default to 172.16.0.0/16. | - - :::note - - If you are editing the cluster in the `cluster.yml` instead of the Rancher UI, note that, cluster configuration directives must be nested under the `rancher_kubernetes_engine_config` directive in `cluster.yml`. For more information, refer to the section on [the config file structure in Rancher v2.3.0+.](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#config-file-structure-in-rancher) - - ::: - -7. Click `Next: Select Instance Type` to choose the instance type that will use for your TKE cluster. - - | Option | Description | - | ---------- | -------------------------------------------------------------------------------------------------------------------- | - | Availability Zone | Choose the availability zone of the VPC region. | - | Subnet | Select the Subnet that you have created within the VPC, and add a new one if you don't have it in the chosen availability zone. | - | Instance Type | From the drop-down chooses the VM instance type that you want to use for the TKE cluster, default to S2.MEDIUM4 (CPU 2 Memory 4 GiB). | - -8. Click `Next: Configure Instance` to configure the VM instance that will use for your TKE cluster. - - Option | Description - -------|------------ - Operating System | The name of the operating system, currently supports Centos7.2x86_64 or ubuntu16.04.1 LTSx86_64 - Security Group | Security group ID, default does not bind any security groups. - Root Disk Type | System disk type. System disk type restrictions are detailed in the [CVM instance configuration](https://cloud.tencent.com/document/product/213/11518). - Root Disk Size | System disk size. Linux system adjustment range is 20 - 50G, step size is 1. - Data Disk Type | Data disk type, default value to the SSD cloud drive - Data Disk Size | Data disk size (GB), the step size is 10 - Band Width Type | Type of bandwidth, PayByTraffic or PayByHour - Band Width | Public network bandwidth (Mbps) - Key Pair | Key id, after associating the key can be used to logging to the VM node - -9. Click **Create**. - -**Result:** - -Your cluster is created and assigned a state of **Provisioning**. Rancher is standing up your cluster. - -You can access your cluster after its state is updated to **Active**. - -**Active** clusters are assigned two Projects: - -- `Default`, containing the `default` namespace -- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces diff --git a/versioned_sidebars/version-2.10-sidebars.json b/versioned_sidebars/version-2.10-sidebars.json index 72cd934fbf6..de8f339d4bb 100644 --- a/versioned_sidebars/version-2.10-sidebars.json +++ b/versioned_sidebars/version-2.10-sidebars.json @@ -434,10 +434,7 @@ "items": [ "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks", "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei" + "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks" ] }, { diff --git a/versioned_sidebars/version-2.11-sidebars.json b/versioned_sidebars/version-2.11-sidebars.json index 155f9b566e0..67fbc6761e2 100644 --- a/versioned_sidebars/version-2.11-sidebars.json +++ b/versioned_sidebars/version-2.11-sidebars.json @@ -434,10 +434,7 @@ "items": [ "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks", "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei" + "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks" ] }, { diff --git a/versioned_sidebars/version-2.12-sidebars.json b/versioned_sidebars/version-2.12-sidebars.json index ab4ce77df65..8ecd9194881 100644 --- a/versioned_sidebars/version-2.12-sidebars.json +++ b/versioned_sidebars/version-2.12-sidebars.json @@ -436,10 +436,7 @@ "items": [ "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks", "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei" + "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks" ] }, { diff --git a/versioned_sidebars/version-2.8-sidebars.json b/versioned_sidebars/version-2.8-sidebars.json index ab494258e6f..bda50220f63 100644 --- a/versioned_sidebars/version-2.8-sidebars.json +++ b/versioned_sidebars/version-2.8-sidebars.json @@ -436,10 +436,7 @@ "items": [ "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks", "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei" + "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks" ] }, { diff --git a/versioned_sidebars/version-2.9-sidebars.json b/versioned_sidebars/version-2.9-sidebars.json index db7c497b4b6..175b20f61e3 100644 --- a/versioned_sidebars/version-2.9-sidebars.json +++ b/versioned_sidebars/version-2.9-sidebars.json @@ -434,10 +434,7 @@ "items": [ "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks", "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/alibaba", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/tencent", - "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/huawei" + "how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/aks" ] }, { From 942717bd89eb0d82656830890f8e35095ecd2b01 Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Wed, 20 Aug 2025 08:03:16 -0700 Subject: [PATCH 4/4] Remove APIs weren't intended to be listed --- openapi/swagger-v2.12.json | 1757 ------------------------------------ 1 file changed, 1757 deletions(-) diff --git a/openapi/swagger-v2.12.json b/openapi/swagger-v2.12.json index 98cbe8c52e1..a11826a68c3 100644 --- a/openapi/swagger-v2.12.json +++ b/openapi/swagger-v2.12.json @@ -5837,1464 +5837,6 @@ "$ref": "#/parameters/pretty-tJGM1-ng" } ] - }, - "/apis/rke.cattle.io/v1/custommachines": { - "get": { - "description": "list objects of kind CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "listRkeCattleIoV1CustomMachineForAllNamespaces", - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachineList" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "list", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "parameters": [ - { - "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J" - }, - { - "$ref": "#/parameters/continue-QfD61s0i" - }, - { - "$ref": "#/parameters/fieldSelector-xIcQKXFG" - }, - { - "$ref": "#/parameters/labelSelector-5Zw57w4C" - }, - { - "$ref": "#/parameters/limit-1NfNmdNH" - }, - { - "$ref": "#/parameters/pretty-tJGM1-ng" - }, - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - }, - { - "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC" - }, - { - "$ref": "#/parameters/sendInitialEvents-rLXlEK_k" - }, - { - "$ref": "#/parameters/timeoutSeconds-yvYezaOC" - }, - { - "$ref": "#/parameters/watch-XNNPZGbK" - } - ] - }, - "/apis/rke.cattle.io/v1/etcdsnapshots": { - "get": { - "description": "list objects of kind ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "listRkeCattleIoV1ETCDSnapshotForAllNamespaces", - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshotList" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "list", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "parameters": [ - { - "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J" - }, - { - "$ref": "#/parameters/continue-QfD61s0i" - }, - { - "$ref": "#/parameters/fieldSelector-xIcQKXFG" - }, - { - "$ref": "#/parameters/labelSelector-5Zw57w4C" - }, - { - "$ref": "#/parameters/limit-1NfNmdNH" - }, - { - "$ref": "#/parameters/pretty-tJGM1-ng" - }, - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - }, - { - "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC" - }, - { - "$ref": "#/parameters/sendInitialEvents-rLXlEK_k" - }, - { - "$ref": "#/parameters/timeoutSeconds-yvYezaOC" - }, - { - "$ref": "#/parameters/watch-XNNPZGbK" - } - ] - }, - "/apis/rke.cattle.io/v1/namespaces/{namespace}/custommachines": { - "get": { - "description": "list objects of kind CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "listRkeCattleIoV1NamespacedCustomMachine", - "parameters": [ - { - "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J" - }, - { - "$ref": "#/parameters/continue-QfD61s0i" - }, - { - "$ref": "#/parameters/fieldSelector-xIcQKXFG" - }, - { - "$ref": "#/parameters/labelSelector-5Zw57w4C" - }, - { - "$ref": "#/parameters/limit-1NfNmdNH" - }, - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - }, - { - "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC" - }, - { - "$ref": "#/parameters/sendInitialEvents-rLXlEK_k" - }, - { - "$ref": "#/parameters/timeoutSeconds-yvYezaOC" - }, - { - "$ref": "#/parameters/watch-XNNPZGbK" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachineList" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "list", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "post": { - "description": "create a CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "createRkeCattleIoV1NamespacedCustomMachine", - "parameters": [ - { - "name": "body", - "in": "body", - "required": true, - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-Qy4HdaTW" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "201": { - "description": "Created", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "202": { - "description": "Accepted", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "post", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "delete": { - "description": "delete collection of CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "deleteRkeCattleIoV1CollectionNamespacedCustomMachine", - "parameters": [ - { - "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J" - }, - { - "$ref": "#/parameters/continue-QfD61s0i" - }, - { - "$ref": "#/parameters/fieldSelector-xIcQKXFG" - }, - { - "$ref": "#/parameters/labelSelector-5Zw57w4C" - }, - { - "$ref": "#/parameters/limit-1NfNmdNH" - }, - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - }, - { - "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC" - }, - { - "$ref": "#/parameters/sendInitialEvents-rLXlEK_k" - }, - { - "$ref": "#/parameters/timeoutSeconds-yvYezaOC" - }, - { - "$ref": "#/parameters/watch-XNNPZGbK" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "deletecollection", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "parameters": [ - { - "$ref": "#/parameters/namespace-vgWSWtn3" - }, - { - "$ref": "#/parameters/pretty-tJGM1-ng" - } - ] - }, - "/apis/rke.cattle.io/v1/namespaces/{namespace}/custommachines/{name}": { - "get": { - "description": "read the specified CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "readRkeCattleIoV1NamespacedCustomMachine", - "parameters": [ - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "get", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "put": { - "description": "replace the specified CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "replaceRkeCattleIoV1NamespacedCustomMachine", - "parameters": [ - { - "name": "body", - "in": "body", - "required": true, - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-Qy4HdaTW" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "201": { - "description": "Created", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "put", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "delete": { - "description": "delete a CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "deleteRkeCattleIoV1NamespacedCustomMachine", - "parameters": [ - { - "$ref": "#/parameters/body-2Y1dVQaQ" - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS" - }, - { - "$ref": "#/parameters/ignoreStoreReadErrorWithClusterBreakingPotential-QbNkfIqj" - }, - { - "$ref": "#/parameters/orphanDependents-uRB25kX5" - }, - { - "$ref": "#/parameters/propagationPolicy-6jk3prlO" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status" - } - }, - "202": { - "description": "Accepted", - "schema": { - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "delete", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "patch": { - "description": "partially update the specified CustomMachine", - "consumes": [ - "application/json-patch+json", - "application/merge-patch+json", - "application/apply-patch+yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "patchRkeCattleIoV1NamespacedCustomMachine", - "parameters": [ - { - "$ref": "#/parameters/body-78PwaGsr" - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-7c6nTn1T" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - }, - { - "$ref": "#/parameters/force-tOGGb0Yi" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "patch", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "parameters": [ - { - "uniqueItems": true, - "type": "string", - "description": "name of the CustomMachine", - "name": "name", - "in": "path", - "required": true - }, - { - "$ref": "#/parameters/namespace-vgWSWtn3" - }, - { - "$ref": "#/parameters/pretty-tJGM1-ng" - } - ] - }, - "/apis/rke.cattle.io/v1/namespaces/{namespace}/custommachines/{name}/status": { - "get": { - "description": "read status of the specified CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "readRkeCattleIoV1NamespacedCustomMachineStatus", - "parameters": [ - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "get", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "put": { - "description": "replace status of the specified CustomMachine", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "replaceRkeCattleIoV1NamespacedCustomMachineStatus", - "parameters": [ - { - "name": "body", - "in": "body", - "required": true, - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-Qy4HdaTW" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "201": { - "description": "Created", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "put", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "patch": { - "description": "partially update status of the specified CustomMachine", - "consumes": [ - "application/json-patch+json", - "application/merge-patch+json", - "application/apply-patch+yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "patchRkeCattleIoV1NamespacedCustomMachineStatus", - "parameters": [ - { - "$ref": "#/parameters/body-78PwaGsr" - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-7c6nTn1T" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - }, - { - "$ref": "#/parameters/force-tOGGb0Yi" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "patch", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - }, - "parameters": [ - { - "uniqueItems": true, - "type": "string", - "description": "name of the CustomMachine", - "name": "name", - "in": "path", - "required": true - }, - { - "$ref": "#/parameters/namespace-vgWSWtn3" - }, - { - "$ref": "#/parameters/pretty-tJGM1-ng" - } - ] - }, - "/apis/rke.cattle.io/v1/namespaces/{namespace}/etcdsnapshots": { - "get": { - "description": "list objects of kind ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "listRkeCattleIoV1NamespacedETCDSnapshot", - "parameters": [ - { - "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J" - }, - { - "$ref": "#/parameters/continue-QfD61s0i" - }, - { - "$ref": "#/parameters/fieldSelector-xIcQKXFG" - }, - { - "$ref": "#/parameters/labelSelector-5Zw57w4C" - }, - { - "$ref": "#/parameters/limit-1NfNmdNH" - }, - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - }, - { - "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC" - }, - { - "$ref": "#/parameters/sendInitialEvents-rLXlEK_k" - }, - { - "$ref": "#/parameters/timeoutSeconds-yvYezaOC" - }, - { - "$ref": "#/parameters/watch-XNNPZGbK" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshotList" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "list", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "post": { - "description": "create an ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "createRkeCattleIoV1NamespacedETCDSnapshot", - "parameters": [ - { - "name": "body", - "in": "body", - "required": true, - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-Qy4HdaTW" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "201": { - "description": "Created", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "202": { - "description": "Accepted", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "post", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "delete": { - "description": "delete collection of ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "deleteRkeCattleIoV1CollectionNamespacedETCDSnapshot", - "parameters": [ - { - "$ref": "#/parameters/allowWatchBookmarks-HC2hJt-J" - }, - { - "$ref": "#/parameters/continue-QfD61s0i" - }, - { - "$ref": "#/parameters/fieldSelector-xIcQKXFG" - }, - { - "$ref": "#/parameters/labelSelector-5Zw57w4C" - }, - { - "$ref": "#/parameters/limit-1NfNmdNH" - }, - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - }, - { - "$ref": "#/parameters/resourceVersionMatch-t8XhRHeC" - }, - { - "$ref": "#/parameters/sendInitialEvents-rLXlEK_k" - }, - { - "$ref": "#/parameters/timeoutSeconds-yvYezaOC" - }, - { - "$ref": "#/parameters/watch-XNNPZGbK" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "deletecollection", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "parameters": [ - { - "$ref": "#/parameters/namespace-vgWSWtn3" - }, - { - "$ref": "#/parameters/pretty-tJGM1-ng" - } - ] - }, - "/apis/rke.cattle.io/v1/namespaces/{namespace}/etcdsnapshots/{name}": { - "get": { - "description": "read the specified ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "readRkeCattleIoV1NamespacedETCDSnapshot", - "parameters": [ - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "get", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "put": { - "description": "replace the specified ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "replaceRkeCattleIoV1NamespacedETCDSnapshot", - "parameters": [ - { - "name": "body", - "in": "body", - "required": true, - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-Qy4HdaTW" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "201": { - "description": "Created", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "put", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "delete": { - "description": "delete an ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "deleteRkeCattleIoV1NamespacedETCDSnapshot", - "parameters": [ - { - "$ref": "#/parameters/body-2Y1dVQaQ" - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/gracePeriodSeconds--K5HaBOS" - }, - { - "$ref": "#/parameters/ignoreStoreReadErrorWithClusterBreakingPotential-QbNkfIqj" - }, - { - "$ref": "#/parameters/orphanDependents-uRB25kX5" - }, - { - "$ref": "#/parameters/propagationPolicy-6jk3prlO" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status" - } - }, - "202": { - "description": "Accepted", - "schema": { - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Status" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "delete", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "patch": { - "description": "partially update the specified ETCDSnapshot", - "consumes": [ - "application/json-patch+json", - "application/merge-patch+json", - "application/apply-patch+yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "patchRkeCattleIoV1NamespacedETCDSnapshot", - "parameters": [ - { - "$ref": "#/parameters/body-78PwaGsr" - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-7c6nTn1T" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - }, - { - "$ref": "#/parameters/force-tOGGb0Yi" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "patch", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "parameters": [ - { - "uniqueItems": true, - "type": "string", - "description": "name of the ETCDSnapshot", - "name": "name", - "in": "path", - "required": true - }, - { - "$ref": "#/parameters/namespace-vgWSWtn3" - }, - { - "$ref": "#/parameters/pretty-tJGM1-ng" - } - ] - }, - "/apis/rke.cattle.io/v1/namespaces/{namespace}/etcdsnapshots/{name}/status": { - "get": { - "description": "read status of the specified ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "readRkeCattleIoV1NamespacedETCDSnapshotStatus", - "parameters": [ - { - "$ref": "#/parameters/resourceVersion-5WAnf1kx" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "get", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "put": { - "description": "replace status of the specified ETCDSnapshot", - "consumes": [ - "application/json", - "application/yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "replaceRkeCattleIoV1NamespacedETCDSnapshotStatus", - "parameters": [ - { - "name": "body", - "in": "body", - "required": true, - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-Qy4HdaTW" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "201": { - "description": "Created", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "put", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "patch": { - "description": "partially update status of the specified ETCDSnapshot", - "consumes": [ - "application/json-patch+json", - "application/merge-patch+json", - "application/apply-patch+yaml" - ], - "produces": [ - "application/json", - "application/yaml" - ], - "schemes": [ - "https" - ], - "tags": [ - "rkeCattleIo_v1" - ], - "operationId": "patchRkeCattleIoV1NamespacedETCDSnapshotStatus", - "parameters": [ - { - "$ref": "#/parameters/body-78PwaGsr" - }, - { - "uniqueItems": true, - "type": "string", - "description": "When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed", - "name": "dryRun", - "in": "query" - }, - { - "$ref": "#/parameters/fieldManager-7c6nTn1T" - }, - { - "uniqueItems": true, - "type": "string", - "description": "fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.", - "name": "fieldValidation", - "in": "query" - }, - { - "$ref": "#/parameters/force-tOGGb0Yi" - } - ], - "responses": { - "200": { - "description": "OK", - "schema": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "401": { - "description": "Unauthorized" - } - }, - "x-kubernetes-action": "patch", - "x-kubernetes-group-version-kind": { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - }, - "parameters": [ - { - "uniqueItems": true, - "type": "string", - "description": "name of the ETCDSnapshot", - "name": "name", - "in": "path", - "required": true - }, - { - "$ref": "#/parameters/namespace-vgWSWtn3" - }, - { - "$ref": "#/parameters/pretty-tJGM1-ng" - } - ] } }, "definitions": { @@ -9450,305 +7992,6 @@ } ] }, - "io.cattle.rke.v1.CustomMachine": { - "description": "CustomMachine represents an unmanaged CAPI\nmachine registered to a Rancher custom cluster.", - "type": "object", - "properties": { - "apiVersion": { - "description": "APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources", - "type": "string" - }, - "kind": { - "description": "Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds", - "type": "string" - }, - "metadata": { - "description": "Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata", - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta" - }, - "spec": { - "description": "Spec represents the desired configuration of the machine.", - "type": "object", - "properties": { - "providerID": { - "description": "ProviderID is a reference to the CAPI Node object corresponding to\nthis machine. This field is automatically set by CAPI during the\nmachine provisioning process." - } - } - }, - "status": { - "description": "Status represents the most recently observed status of the machine.", - "type": "object", - "properties": { - "addresses": { - "description": "Addresses contains the associated addresses for the machine.", - "type": "array", - "items": { - "description": "MachineAddress contains information for the node's address.", - "type": "object", - "required": [ - "address", - "type" - ], - "properties": { - "address": { - "description": "address is the machine address.", - "type": "string", - "maxLength": 256, - "minLength": 1 - }, - "type": { - "description": "type is the machine address type, one of Hostname, ExternalIP, InternalIP, ExternalDNS or InternalDNS.", - "type": "string", - "enum": [ - "Hostname", - "ExternalIP", - "InternalIP", - "ExternalDNS", - "InternalDNS" - ] - } - } - } - }, - "conditions": { - "description": "Conditions is a representation of the current state of the machine.", - "type": "array", - "items": { - "type": "object", - "required": [ - "status", - "type" - ], - "properties": { - "lastTransitionTime": { - "description": "Last time the condition transitioned from one status to another.", - "type": "string" - }, - "lastUpdateTime": { - "description": "The last time this condition was updated.", - "type": "string" - }, - "message": { - "description": "Human-readable message indicating details about last transition", - "type": "string" - }, - "reason": { - "description": "The reason for the condition's last transition.", - "type": "string" - }, - "status": { - "description": "Status of the condition, one of True, False, Unknown.", - "type": "string" - }, - "type": { - "description": "Type of cluster condition.", - "type": "string" - } - } - } - }, - "ready": { - "description": "Ready indicates that the machine infrastructure is fully provisioned,\nand is a requirement of the Cluster API contract. The value of this\nfield is never updated after provisioning has completed.\nPlease use Conditions to determine the current state of the machine.", - "type": "boolean" - } - } - } - }, - "x-kubernetes-group-version-kind": [ - { - "group": "rke.cattle.io", - "kind": "CustomMachine", - "version": "v1" - } - ] - }, - "io.cattle.rke.v1.CustomMachineList": { - "description": "CustomMachineList is a list of CustomMachine", - "type": "object", - "required": [ - "items" - ], - "properties": { - "apiVersion": { - "description": "APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources", - "type": "string" - }, - "items": { - "description": "List of custommachines. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md", - "type": "array", - "items": { - "$ref": "#/definitions/io.cattle.rke.v1.CustomMachine" - } - }, - "kind": { - "description": "Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds", - "type": "string" - }, - "metadata": { - "description": "Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds", - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta" - } - }, - "x-kubernetes-group-version-kind": [ - { - "group": "rke.cattle.io", - "kind": "CustomMachineList", - "version": "v1" - } - ] - }, - "io.cattle.rke.v1.ETCDSnapshot": { - "description": "ETCDSnapshot is the top-level resource representing a snapshot operation.", - "type": "object", - "properties": { - "apiVersion": { - "description": "APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources", - "type": "string" - }, - "kind": { - "description": "Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds", - "type": "string" - }, - "metadata": { - "description": "Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata", - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta" - }, - "snapshotFile": { - "description": "SnapshotFile holds metadata about the snapshot file produced by this snapshot operation.", - "type": "object", - "properties": { - "createdAt": { - "description": "CreatedAt is the timestamp when the snapshot was created.", - "type": "string", - "format": "date-time" - }, - "location": { - "description": "Location is the absolute file:// or s3:// URI address of the snapshot.", - "type": "string" - }, - "message": { - "description": "Message is a string detailing the encountered error during snapshot creation if specified.", - "type": "string" - }, - "metadata": { - "description": "Metadata contains a base64-encoded, gzipped snapshot of the cluster spec at the time the snapshot was taken.", - "type": "string" - }, - "name": { - "description": "Name is the full snapshot name. It consists of the cluster name prefix,\nfollowed by the base snapshot identifier and ends with an optional storage suffix (e.g. \"s3\").\nThe typical format is:\n \u003ccluster\u003e-etcd-snapshot-\u003ccluster\u003e-\u003cnodepool\u003e-\u003cuniqueid\u003e-\u003ctimestamp\u003e[-\u003cstorage-type\u003e]\nThe base snapshot identifier follows:\n etcd-snapshot-\u003ccluster\u003e-\u003cnodepool\u003e-\u003cuniqueid\u003e-\u003ctimestamp\u003e", - "type": "string" - }, - "nodeName": { - "description": "NodeName is the name of the downstream node where the snapshot was created.", - "type": "string" - }, - "s3": { - "description": "S3 holds metadata about the S3 destination if the snapshot is stored remotely. If nil, the snapshot\nis assumed to be stored locally and associated with the owning CAPI machine.", - "type": "object", - "properties": { - "bucket": { - "description": "Bucket is the name of the S3 bucket used for snapshot operations.\nIf this field is not explicitly set, the 'defaultBucket' value from the referenced CloudCredential will be used.\nAn empty bucket name will cause a 'failed to initialize S3 client: s3 bucket name was not set' error.", - "maxLength": 63 - }, - "cloudCredentialName": { - "description": "CloudCredentialName is the name of the secret containing the\ncredentials used to access the S3 bucket.\nThe secret is expected to have the following keys:\n- accessKey [required]\n- secretKey [required]\n- defaultRegion\n- defaultEndpoint\n- defaultEndpointCA\n- defaultSkipSSLVerify\n- defaultBucket\n- defaultFolder\nFields set directly in this spec (`ETCDSnapshotS3`) take precedence over the corresponding\nvalues from the CloudCredential secret. This field must be in the format of \"namespace:name\"." - }, - "endpoint": { - "description": "Endpoint is the S3 endpoint used for snapshot operations.\nIf this field is not explicitly set, the 'defaultEndpoint' value from the referenced CloudCredential will be used." - }, - "endpointCA": { - "description": "EndpointCA is the CA certificate for validating the S3 endpoint.\nThis can be either a file path (e.g., \"/etc/ssl/certs/my-ca.crt\")\nor the CA certificate content, in base64-encoded or plain PEM format.\nIf this field is not explicitly set, the 'defaultEndpointCA' value from the referenced CloudCredential will be used." - }, - "folder": { - "description": "Folder is the name of the S3 folder used for snapshot operations.\nIf this field is not explicitly set, the folder from the referenced CloudCredential will be used." - }, - "region": { - "description": "Region is the S3 region used for snapshot operations. (e.g., \"us-east-1\").\nIf this field is not explicitly set, the 'defaultRegion' value from the referenced CloudCredential will be used." - }, - "skipSSLVerify": { - "description": "SkipSSLVerify defines whether TLS certificate verification is disabled.\nIf this field is not explicitly set, the 'defaultSkipSSLVerify' value\nfrom the referenced CloudCredential will be used.", - "type": "boolean" - } - } - }, - "size": { - "description": "Size is the size of the snapshot file in bytes.", - "type": "integer", - "format": "int64" - }, - "status": { - "description": "Status represents the current state of the snapshot, such as \"successful\" or \"failed\".", - "type": "string" - } - } - }, - "spec": { - "description": "Spec defines the desired state of the ETCDSnapshot.", - "type": "object", - "properties": { - "clusterName": { - "description": "ClusterName is the name of the cluster (cluster.provisioning.cattle.io) for which this snapshot was taken.", - "type": "string" - } - } - }, - "status": { - "description": "Status contains information about the current state of the snapshot operation.", - "type": "object", - "required": [ - "missing" - ], - "properties": { - "missing": { - "description": "This field is currently unused but retained for backward compatibility or future use.", - "type": "boolean" - } - } - } - }, - "x-kubernetes-group-version-kind": [ - { - "group": "rke.cattle.io", - "kind": "ETCDSnapshot", - "version": "v1" - } - ] - }, - "io.cattle.rke.v1.ETCDSnapshotList": { - "description": "ETCDSnapshotList is a list of ETCDSnapshot", - "type": "object", - "required": [ - "items" - ], - "properties": { - "apiVersion": { - "description": "APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources", - "type": "string" - }, - "items": { - "description": "List of etcdsnapshots. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md", - "type": "array", - "items": { - "$ref": "#/definitions/io.cattle.rke.v1.ETCDSnapshot" - } - }, - "kind": { - "description": "Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds", - "type": "string" - }, - "metadata": { - "description": "Standard list metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds", - "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ListMeta" - } - }, - "x-kubernetes-group-version-kind": [ - { - "group": "rke.cattle.io", - "kind": "ETCDSnapshotList", - "version": "v1" - } - ] - }, "io.k8s.apimachinery.pkg.apis.meta.v1.Condition": { "description": "Condition contains details for one aspect of the current state of this API Resource.", "type": "object",