rancher
/
rke1-docs
mirror of https://github.com/rancher/rke1-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix broken links

This commit is contained in:
Billy Tat 2023-03-13 16:48:42 -07:00
parent 31ff12847f
commit 1e4d12c61d
8 changed files with 46 additions and 46 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/config-options/cloud-providers/vsphere/enabling-uuid/enabling-uuid.md
View File

@ -5,7 +5,7 @@ weight: 2
In order to provision nodes with RKE, all nodes must be configured with disk UUIDs. This is required so that attached VMDKs present a consistent UUID to the VM, allowing the disk to be mounted properly. In order to provision nodes with RKE, all nodes must be configured with disk UUIDs. This is required so that attached VMDKs present a consistent UUID to the VM, allowing the disk to be mounted properly.
Depending on whether you are provisioning the VMs using the [vSphere node driver]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/vsphere) in Rancher or using your own scripts or third-party tools, there are different methods available to enable disk UUIDs for VMs: Depending on whether you are provisioning the VMs using the [vSphere node driver](https://ranchermanager.docs.rancher.com/pages-for-subheaders/launch-kubernetes-with-ranchernode-pools/vsphere) in Rancher or using your own scripts or third-party tools, there are different methods available to enable disk UUIDs for VMs:
- [Using the vSphere console](#using-the-vsphere-console) - [Using the vSphere console](#using-the-vsphere-console)
- [Using the GOVC CLI tool](#using-the-govc-cli-tool) - [Using the GOVC CLI tool](#using-the-govc-cli-tool)
@ -32,4 +32,4 @@ $ govc vm.change -vm <vm-path> -e disk.enableUUID=TRUE
In Rancher v2.0.4+, disk UUIDs are enabled in vSphere node templates by default. In Rancher v2.0.4+, disk UUIDs are enabled in vSphere node templates by default.
If you are using Rancher before v2.0.4, refer to the [vSphere node template documentation.]({{<baseurl>}}/rancher/v2.0-v2.4/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/prior-to-2.0.4//) for details on how to enable a UUID with a Rancher node template. If you are using Rancher before v2.0.4, refer to the [vSphere node template documentation.](https://ranchermanager.docs.rancher.com/v2.0-v2.4/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/vsphere/prior-to-v2.0.4) for details on how to enable a UUID with a Rancher node template.

4
docs/config-options/cloud-providers/vsphere/troubleshooting/troubleshooting.md
View File

@ -8,11 +8,11 @@ If you are experiencing issues while provisioning a cluster with enabled vSphere
- controller-manager (Manages volumes in vCenter) - controller-manager (Manages volumes in vCenter)
- kubelet: (Mounts vSphere volumes to pods) - kubelet: (Mounts vSphere volumes to pods)
If your cluster is not configured with external [Cluster Logging]({{<baseurl>}}/rancher/v2.x//en/cluster-admin/tools//logging/), you will need to SSH into nodes to get the logs of the `kube-controller-manager` (running on one of the control plane nodes) and the `kubelet` (pertaining to the node where the stateful pod has been scheduled). If your cluster is not configured with external [Cluster Logging](https://ranchermanager.docs.rancher.com/pages-for-subheaders/logging), you will need to SSH into nodes to get the logs of the `kube-controller-manager` (running on one of the control plane nodes) and the `kubelet` (pertaining to the node where the stateful pod has been scheduled).
The easiest way to create a SSH session with a node is the Rancher CLI tool. The easiest way to create a SSH session with a node is the Rancher CLI tool.
1. [Configure the Rancher CLI]({{<baseurl>}}/rancher/v2.x/en/cli/) for your cluster. 1. [Configure the Rancher CLI](https://ranchermanager.docs.rancher.com/pages-for-subheaders/cli-with-rancher) for your cluster.
2. Run the following command to get a shell to the corresponding nodes: 2. Run the following command to get a shell to the corresponding nodes:
```shell ```shell

4
docs/config-options/cloud-providers/vsphere/vsphere.md
View File

@ -13,8 +13,8 @@ When provisioning Kubernetes using RKE CLI or using [RKE clusters]({{< baseurl >
- **Configuration:** For details on vSphere configuration in RKE, refer to the [configuration reference.](config-options/cloud-providers/vsphere/config-reference) - **Configuration:** For details on vSphere configuration in RKE, refer to the [configuration reference.](config-options/cloud-providers/vsphere/config-reference)
- **Troubleshooting:** For guidance on troubleshooting a cluster with the vSphere cloud provider enabled, refer to the [troubleshooting section.](config-options/cloud-providers/vsphere/troubleshooting) - **Troubleshooting:** For guidance on troubleshooting a cluster with the vSphere cloud provider enabled, refer to the [troubleshooting section.](config-options/cloud-providers/vsphere/troubleshooting)
- **Storage:** If you are setting up storage, see the [official vSphere documentation on storage for Kubernetes,](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/) or the [official Kubernetes documentation on persistent volumes.](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) If you are using Rancher, refer to the [Rancher documentation on provisioning storage in vSphere.]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/volumes-and-storage/examples/vsphere) - **Storage:** If you are setting up storage, see the [official vSphere documentation on storage for Kubernetes,](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/) or the [official Kubernetes documentation on persistent volumes.](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) If you are using Rancher, refer to the [Rancher documentation on provisioning storage in vSphere.](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/provisioning-storage-examples/vsphere-storage#docusaurus_skipToContent_fallback)
- **For Rancher users:** Refer to the Rancher documentation on [creating vSphere Kubernetes clusters]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/vsphere) and [provisioning storage.]({{<baseurl>}}/rancher/v2.x/en/cluster-admin/volumes-and-storage/examples/vsphere) - **For Rancher users:** Refer to the Rancher documentation on [creating vSphere Kubernetes clusters](https://ranchermanager.docs.rancher.com/pages-for-subheaders/launch-kubernetes-with-ranchernode-pools/vsphere) and [provisioning storage.](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/provisioning-storage-examples/vsphere-storage#docusaurus_skipToContent_fallback)
# Prerequisites # Prerequisites

2
docs/config-options/secrets-encryption/secrets-encryption.md
View File

@ -20,7 +20,7 @@ RKE provides users with two paths of configuration to enable at-rest data encryp
Both configuration options can be added during initial cluster provisioning or by updating an existing cluster. Both configuration options can be added during initial cluster provisioning or by updating an existing cluster.
To utilize this feature, a new field `secrets_encryption_config` is added to the [Kubernetes API service configuration]({{<baseurl>}}//rke/latest/en/config-options/services/#kubernetes-api-server). A full custom configuration looks like this: To utilize this feature, a new field `secrets_encryption_config` is added to the [Kubernetes API service configuration](../services/services.md#kubernetes-api-server). A full custom configuration looks like this:
```yaml ```yaml
services: services:

10
docs/config-options/services/services.md
View File

@ -6,7 +6,7 @@ weight: 230
To deploy Kubernetes, RKE deploys several core components or services in Docker containers on the nodes. Based on the roles of the node, the containers deployed may be different. To deploy Kubernetes, RKE deploys several core components or services in Docker containers on the nodes. Based on the roles of the node, the containers deployed may be different.
>**Note:** All services support <b>additional custom arguments, Docker mount binds, and extra environment variables.</b> >**Note:** All services support <b>additional custom arguments, Docker mount binds, and extra environment variables.</b>
> >
>To configure advanced options for Kubernetes services such as `kubelet`, `kube-controller`, and `kube-apiserver` that are not documented below, see the [`extra_args` documentation](config-options/services/services-extras/) for more details. >To configure advanced options for Kubernetes services such as `kubelet`, `kube-controller`, and `kube-apiserver` that are not documented below, see the [`extra_args` documentation](config-options/services/services-extras/) for more details.
@ -31,7 +31,7 @@ By default, RKE will deploy a new etcd service, but you can also run Kubernetes
## Kubernetes API Server ## Kubernetes API Server
> **Note for Rancher 2 users** If you are configuring Cluster Options using a [Config File]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/#cluster-config-file) when creating [Rancher Launched Kubernetes]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/), the names of services should contain underscores only: `kube_api`. This only applies to Rancher v2.0.5 and v2.0.6. > **Note for Rancher 2 users** If you are configuring Cluster Options using a [Config File](https://ranchermanager.docs.rancher.com/reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration#rke-cluster-config-file-reference) when creating [Rancher Launched Kubernetes](https://ranchermanager.docs.rancher.com/pages-for-subheaders/launch-kubernetes-with-rancher), the names of services should contain underscores only: `kube_api`. This only applies to Rancher v2.0.5 and v2.0.6.
The [Kubernetes API](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/) REST service, which handles requests and data for all Kubernetes objects and provide shared state for all the other Kubernetes components. The [Kubernetes API](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/) REST service, which handles requests and data for all Kubernetes objects and provide shared state for all the other Kubernetes components.
@ -60,10 +60,10 @@ RKE supports the following options for the `kube-api` service :
- **Pod Security Policy** (`pod_security_policy`) - An option to enable the [Kubernetes Pod Security Policy](https://kubernetes.io/docs/concepts/policy/pod-security-policy/). By default, we do not enable pod security policies as it is set to `false`. - **Pod Security Policy** (`pod_security_policy`) - An option to enable the [Kubernetes Pod Security Policy](https://kubernetes.io/docs/concepts/policy/pod-security-policy/). By default, we do not enable pod security policies as it is set to `false`.
> **Note:** If you set `pod_security_policy` value to `true`, RKE will configure an open policy to allow any pods to work on the cluster. You will need to configure your own policies to fully utilize PSP. > **Note:** If you set `pod_security_policy` value to `true`, RKE will configure an open policy to allow any pods to work on the cluster. You will need to configure your own policies to fully utilize PSP.
- **Always Pull Images** (`always_pull_images`) - Enable `AlwaysPullImages` Admission controller plugin. Enabling `AlwaysPullImages` is a security best practice. It forces Kubernetes to validate the image and pull credentials with the remote image registry. Local image layer cache will still be used, but it does add a small bit of overhead when launching containers to pull and compare image hashes. _Note: Available as of v0.2.0_ - **Always Pull Images** (`always_pull_images`) - Enable `AlwaysPullImages` Admission controller plugin. Enabling `AlwaysPullImages` is a security best practice. It forces Kubernetes to validate the image and pull credentials with the remote image registry. Local image layer cache will still be used, but it does add a small bit of overhead when launching containers to pull and compare image hashes. _Note: Available as of v0.2.0_
- **Secrets Encryption Config** (`secrets_encryption_config`) - Manage Kubernetes at-rest data encryption. Documented [here]({{<baseurl>}}//rke/latest/en/config-options/secrets-encryption) - **Secrets Encryption Config** (`secrets_encryption_config`) - Manage Kubernetes at-rest data encryption. Documented [here](../secrets-encryption/secrets-encryption.md)
## Kubernetes Controller Manager ## Kubernetes Controller Manager
> **Note for Rancher 2 users** If you are configuring Cluster Options using a [Config File]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/#cluster-config-file) when creating [Rancher Launched Kubernetes]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/), the names of services should contain underscores only: `kube_controller`. This only applies to Rancher v2.0.5 and v2.0.6. > **Note for Rancher 2 users** If you are configuring Cluster Options using a [Config File](https://ranchermanager.docs.rancher.com/reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration#rke-cluster-config-file-reference) when creating [Rancher Launched Kubernetes](https://ranchermanager.docs.rancher.com/pages-for-subheaders/launch-kubernetes-with-rancher), the names of services should contain underscores only: `kube_controller`. This only applies to Rancher v2.0.5 and v2.0.6.
The [Kubernetes Controller Manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/) service is the component responsible for running Kubernetes main control loops. The controller manager monitors the cluster desired state through the Kubernetes API server and makes the necessary changes to the current state to reach the desired state. The [Kubernetes Controller Manager](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/) service is the component responsible for running Kubernetes main control loops. The controller manager monitors the cluster desired state through the Kubernetes API server and makes the necessary changes to the current state to reach the desired state.
@ -107,7 +107,7 @@ RKE supports the following options for the `kubelet` service:
- **Cluster Domain** (`cluster_domain`) - The [base domain](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/) for the cluster. All services and DNS records created on the cluster. By default, the domain is set to `cluster.local`. - **Cluster Domain** (`cluster_domain`) - The [base domain](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/) for the cluster. All services and DNS records created on the cluster. By default, the domain is set to `cluster.local`.
- **Cluster DNS Server** (`cluster_dns_server`) - The IP address assigned to the DNS service endpoint within the cluster. DNS queries will be sent to this IP address which is used by KubeDNS. The default value for this option is `10.43.0.10` - **Cluster DNS Server** (`cluster_dns_server`) - The IP address assigned to the DNS service endpoint within the cluster. DNS queries will be sent to this IP address which is used by KubeDNS. The default value for this option is `10.43.0.10`
- **Fail if Swap is On** (`fail_swap_on`) - In Kubernetes, the default behavior for the kubelet is to **fail** if swap is enabled on the node. RKE does **not** follow this default and allows deployments on nodes with swap enabled. By default, the value is `false`. If you'd like to revert to the default kubelet behavior, set this option to `true`. - **Fail if Swap is On** (`fail_swap_on`) - In Kubernetes, the default behavior for the kubelet is to **fail** if swap is enabled on the node. RKE does **not** follow this default and allows deployments on nodes with swap enabled. By default, the value is `false`. If you'd like to revert to the default kubelet behavior, set this option to `true`.
- **Generate Serving Certificate** (`generate_serving_certificate`) - Generate a certificate signed by the `kube-ca` Certificate Authority for the kubelet to use as a server certificate. The default value for this option is `false`. Before enabling this option, please read [the requirements](#kubelet-serving-certificate-requirements) - **Generate Serving Certificate** (`generate_serving_certificate`) - Generate a certificate signed by the `kube-ca` Certificate Authority for the kubelet to use as a server certificate. The default value for this option is `false`. Before enabling this option, please read [the requirements](#kubelet-serving-certificate-requirements)
### Kubelet Serving Certificate Requirements ### Kubelet Serving Certificate Requirements

14
docs/example-yamls/example-yamls.md
View File

@ -7,7 +7,7 @@ aliases:
There are lots of different [configuration options](config-options/) that can be set in the cluster configuration file for RKE. Here are some examples of files: There are lots of different [configuration options](config-options/) that can be set in the cluster configuration file for RKE. Here are some examples of files:
> **Note for Rancher 2 users** If you are configuring Cluster Options using a [Config File]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/#cluster-config-file) when creating [Rancher Launched Kubernetes]({{<baseurl>}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/), the names of services should contain underscores only: `kube_api` and `kube_controller`. This only applies to Rancher v2.0.5 and v2.0.6. > **Note for Rancher 2 users** If you are configuring Cluster Options using a [Config File](https://ranchermanager.docs.rancher.com/reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration#rke-cluster-config-file-reference) when creating [Rancher Launched Kubernetes](https://ranchermanager.docs.rancher.com/pages-for-subheaders/launch-kubernetes-with-rancher), the names of services should contain underscores only: `kube_api` and `kube_controller`. This only applies to Rancher v2.0.5 and v2.0.6.
## Minimal `cluster.yml` example ## Minimal `cluster.yml` example
@ -62,8 +62,8 @@ nodes:
ignore_docker_version: false ignore_docker_version: false
# Enable running cri-dockerd # Enable running cri-dockerd
# Up to Kubernetes 1.23, kubelet contained code called dockershim # Up to Kubernetes 1.23, kubelet contained code called dockershim
# to support Docker runtime. The replacement is called cri-dockerd # to support Docker runtime. The replacement is called cri-dockerd
# and should be enabled if you want to keep using Docker as your # and should be enabled if you want to keep using Docker as your
# container runtime # container runtime
# Only available to enable in Kubernetes 1.21 and higher # Only available to enable in Kubernetes 1.21 and higher
@ -101,7 +101,7 @@ bastion_host:
# #
# -----END RSA PRIVATE KEY----- # -----END RSA PRIVATE KEY-----
# Set the name of the Kubernetes cluster # Set the name of the Kubernetes cluster
cluster_name: mycluster cluster_name: mycluster
@ -122,7 +122,7 @@ cluster_name: mycluster
kubernetes_version: v1.10.3-rancher2 kubernetes_version: v1.10.3-rancher2
# System Images are defaulted to a tag that is mapped to a specific # System Images are defaulted to a tag that is mapped to a specific
# Kubernetes Version and not required in a cluster.yml. # Kubernetes Version and not required in a cluster.yml.
# Each individual system image can be specified if you want to use a different tag. # Each individual system image can be specified if you want to use a different tag.
# #
# For RKE v0.2.x and below, the map of Kubernetes versions and their system images is # For RKE v0.2.x and below, the map of Kubernetes versions and their system images is
@ -176,7 +176,7 @@ services:
# This must match the service_cluster_ip_range in kube-controller # This must match the service_cluster_ip_range in kube-controller
service_cluster_ip_range: 10.43.0.0/16 service_cluster_ip_range: 10.43.0.0/16
# Expose a different port range for NodePort services # Expose a different port range for NodePort services
service_node_port_range: 30000-32767 service_node_port_range: 30000-32767
pod_security_policy: false pod_security_policy: false
# Encrypt secret data at Rest # Encrypt secret data at Rest
# Available as of v0.3.1 # Available as of v0.3.1
@ -383,7 +383,7 @@ ingress:
strategy: RollingUpdate strategy: RollingUpdate
rollingUpdate: rollingUpdate:
maxUnavailable: 5 maxUnavailable: 5
# All add-on manifests MUST specify a namespace # All add-on manifests MUST specify a namespace
addons: |- addons: |-
--- ---

52
docs/os/os.md
View File

@ -2,15 +2,15 @@
title: Requirements title: Requirements
weight: 5 weight: 5
--- ---
**In this section:** **In this section:**
<!-- TOC --> <!-- TOC -->
- [Operating System](#operating-system) - [Operating System](#operating-system)
- [General Linux Requirements](#general-linux-requirements) - [General Linux Requirements](#general-linux-requirements)
- [SUSE Linux Enterprise Server (SLES) / openSUSE](#suse-linux-enterprise-server-sles-opensuse) - [SUSE Linux Enterprise Server (SLES) / openSUSE](#suse-linux-enterprise-server-sles-opensuse)
- [Using Upstream Docker](#using-upstream-docker) [Using Upstream Docker](#using-upstream-docker)
- [Using SUSE/openSUSE packaged Docker](#using-suse-opensuse-packaged-docker) - [Using SUSE/openSUSE packaged Docker](#using-suse-opensuse-packaged-docker)
- [Adding the Software Repository for Docker](#adding-the-software-repository-for-docker) [Adding the Software Repository for Docker](#adding-the-software-repository-for-docker)
- [openSUSE MicroOS/Kubic (Atomic)](#opensuse-microos-kubic-atomic) - [openSUSE MicroOS/Kubic (Atomic)](#opensuse-microos-kubic-atomic)
- [openSUSE MicroOS](#opensuse-microos) - [openSUSE MicroOS](#opensuse-microos)
- [openSUSE Kubic](#opensuse-kubic) - [openSUSE Kubic](#opensuse-kubic)
@ -30,7 +30,7 @@ weight: 5
- [Hardware](#hardware) - [Hardware](#hardware)
- [Worker Role](#worker-role) - [Worker Role](#worker-role)
- [Large Kubernetes Clusters](#large-kubernetes-clusters) - [Large Kubernetes Clusters](#large-kubernetes-clusters)
- [Etcd clusters](#etcd-clusters) - [Etcd clusters](#etcd-clusters)
- [Ports](#ports) - [Ports](#ports)
- [Opening port TCP/6443 using `iptables`](#opening-port-tcp-6443-using-iptables) - [Opening port TCP/6443 using `iptables`](#opening-port-tcp-6443-using-iptables)
- [Opening port TCP/6443 using `firewalld`](#opening-port-tcp-6443-using-firewalld) - [Opening port TCP/6443 using `firewalld`](#opening-port-tcp-6443-using-firewalld)
@ -49,8 +49,8 @@ RKE runs on almost any Linux OS with Docker installed. For details on which OS a
``` ```
usermod -aG docker <user_name> usermod -aG docker <user_name>
``` ```
> **Note:** Users added to the `docker` group are granted effective root permissions on the host by means of the Docker API. Only choose a user that is intended for this purpose and has its credentials and access properly secured. > **Note:** Users added to the `docker` group are granted effective root permissions on the host by means of the Docker API. Only choose a user that is intended for this purpose and has its credentials and access properly secured.
See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) to see how you can configure access to Docker without using the `root` user. See [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user) to see how you can configure access to Docker without using the `root` user.
@ -72,9 +72,9 @@ net.bridge.bridge-nf-call-iptables=1
### SUSE Linux Enterprise Server (SLES) / openSUSE ### SUSE Linux Enterprise Server (SLES) / openSUSE
If you are using SUSE Linux Enterprise Server or openSUSE follow the instructions below. If you are using SUSE Linux Enterprise Server or openSUSE follow the instructions below.
#### Using upstream Docker #### Using upstream Docker
If you are using upstream Docker, the package name is `docker-ce` or `docker-ee`. You can check the installed package by executing: If you are using upstream Docker, the package name is `docker-ce` or `docker-ee`. You can check the installed package by executing:
``` ```
@ -83,18 +83,18 @@ rpm -q docker-ce
When using the upstream Docker packages, please follow [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user). When using the upstream Docker packages, please follow [Manage Docker as a non-root user](https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user).
#### Using SUSE/openSUSE packaged docker #### Using SUSE/openSUSE packaged docker
If you are using the Docker package supplied by SUSE/openSUSE, the package name is `docker`. You can check the installed package by executing: If you are using the Docker package supplied by SUSE/openSUSE, the package name is `docker`. You can check the installed package by executing:
``` ```
rpm -q docker rpm -q docker
``` ```
#### Adding the Software repository for docker #### Adding the Software repository for docker
In SUSE Linux Enterprise Server 15 SP2 docker is found in the Containers module. In SUSE Linux Enterprise Server 15 SP2 docker is found in the Containers module.
This module will need to be added before istalling docker. This module will need to be added before istalling docker.
To list available modules you can run SUSEConnect to list the extensions and the activation command To list available modules you can run SUSEConnect to list the extensions and the activation command
``` ```
node:~ # SUSEConnect --list-extensions node:~ # SUSEConnect --list-extensions
AVAILABLE EXTENSIONS AND MODULES AVAILABLE EXTENSIONS AND MODULES
@ -133,23 +133,23 @@ user@node:~> docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
user@node:~> user@node:~>
``` ```
### openSUSE MicroOS/Kubic (Atomic) ### openSUSE MicroOS/Kubic (Atomic)
Consult the project pages for openSUSE MicroOS and Kubic for installation Consult the project pages for openSUSE MicroOS and Kubic for installation
#### openSUSE MicroOS #### openSUSE MicroOS
Designed to host container workloads with automated administration & patching. Installing openSUSE MicroOS you get a quick, small environment for deploying Containers, or any other workload that benefits from Transactional Updates. As rolling release distribution the software is always up-to-date. Designed to host container workloads with automated administration & patching. Installing openSUSE MicroOS you get a quick, small environment for deploying Containers, or any other workload that benefits from Transactional Updates. As rolling release distribution the software is always up-to-date.
https://microos.opensuse.org https://microos.opensuse.org
#### openSUSE Kubic #### openSUSE Kubic
Based on openSUSE MicroOS, designed with the same things in mind but is focused on being a Certified Kubernetes Distribution. Based on openSUSE MicroOS, designed with the same things in mind but is focused on being a Certified Kubernetes Distribution.
https://kubic.opensuse.org https://kubic.opensuse.org
Installation instructions: Installation instructions:
https://kubic.opensuse.org/blog/2021-02-08-MicroOS-Kubic-Rancher-RKE/ https://kubic.opensuse.org/blog/2021-02-08-MicroOS-Kubic-Rancher-RKE/
### Red Hat Enterprise Linux (RHEL) / Oracle Linux (OL) / CentOS ### Red Hat Enterprise Linux (RHEL) / Oracle Linux (OL) / CentOS
If using Red Hat Enterprise Linux, Oracle Linux or CentOS, you cannot use the `root` user as [SSH user](config-options/nodes/#ssh-user) due to [Bugzilla 1527565](https://bugzilla.redhat.com/show_bug.cgi?id=1527565). Please follow the instructions below how to setup Docker correctly, based on the way you installed Docker on the node. If using Red Hat Enterprise Linux, Oracle Linux or CentOS, you cannot use the `root` user as [SSH user](config-options/nodes/#ssh-user) due to [Bugzilla 1527565](https://bugzilla.redhat.com/show_bug.cgi?id=1527565). Please follow the instructions below how to setup Docker correctly, based on the way you installed Docker on the node.
>**Note:** In RHEL 8.4, two extra services are included on the NetworkManager: `nm-cloud-setup.service` and `nm-cloud-setup.timer`. These services add a routing table that interferes with the CNI plugin's configuration. If these services are enabled, you must disable them using the command below, and then reboot the node to restore connectivity: >**Note:** In RHEL 8.4, two extra services are included on the NetworkManager: `nm-cloud-setup.service` and `nm-cloud-setup.timer`. These services add a routing table that interferes with the CNI plugin's configuration. If these services are enabled, you must disable them using the command below, and then reboot the node to restore connectivity:
> >
> ``` > ```
systemctl disable nm-cloud-setup.service nm-cloud-setup.timer systemctl disable nm-cloud-setup.service nm-cloud-setup.timer
reboot reboot
@ -240,7 +240,7 @@ rancher_kubernetes_engine_config:
kube-controller: kube-controller:
extra_args: extra_args:
flex-volume-plugin-dir: /opt/kubernetes/kubelet-plugins/volume/exec/ flex-volume-plugin-dir: /opt/kubernetes/kubelet-plugins/volume/exec/
``` ```
{{% /tab %}} {{% /tab %}}
{{% tab "Calico"%}} {{% tab "Calico"%}}
@ -285,7 +285,7 @@ Each Kubernetes version supports different Docker versions. The Kubernetes relea
### Installing Docker ### Installing Docker
Refer to [Installing Docker]({{<baseurl>}}/rancher/v2.5/en/installation/requirements/installing-docker/) Refer to [Installing Docker](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-requirements/install-docker)
### Checking the Installed Docker Version ### Checking the Installed Docker Version
@ -297,7 +297,7 @@ This section describes the hardware requirements for the worker role, large Kube
### Worker Role ### Worker Role
The hardware requirements for nodes with the `worker` role mostly depend on your workloads. The minimum to run the Kubernetes node components is 1 CPU (core) and 1GB of memory. The hardware requirements for nodes with the `worker` role mostly depend on your workloads. The minimum to run the Kubernetes node components is 1 CPU (core) and 1GB of memory.
Regarding CPU and memory, it is recommended that the different planes of Kubernetes clusters (etcd, controlplane, and workers) should be hosted on different nodes so that they can scale separately from each other. Regarding CPU and memory, it is recommended that the different planes of Kubernetes clusters (etcd, controlplane, and workers) should be hosted on different nodes so that they can scale separately from each other.

2
docs/troubleshooting/provisioning-errors/provisioning-errors.md
View File

@ -5,7 +5,7 @@ weight: 200
### Failed to get job complete status ### Failed to get job complete status
Most common reason for this error is that a node is having issues that block the deploy job from completing successfully. See [Get node conditions]({{<baseurl>}}/rancher/v2.x/en/troubleshooting/kubernetes-resources/#get-node-conditions) how to check node conditions. Most common reason for this error is that a node is having issues that block the deploy job from completing successfully. See [Get node conditions](https://ranchermanager.docs.rancher.com/troubleshooting/other-troubleshooting-tips/kubernetes-resources#get-node-conditions) how to check node conditions.
You can also retrieve the log from the job to see if it has an indication of the error, make sure you replace `rke-network-plugin-deploy-job` with the job name from the error: You can also retrieve the log from the job to see if it has an indication of the error, make sure you replace `rke-network-plugin-deploy-job` with the job name from the error: