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-05-02 16:55:50 -07:00
parent 74c8ccf74a
commit 7795b61e3c
4 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/config-options/private-registries/private-registries.md
View File

@ -33,7 +33,7 @@ url: 1.1.1.1:5555/artifactory
### Default Registry ### Default Registry
As of v0.1.10, RKE supports specifying a default registry from the list of private registries to be used with all [system images](config-options/system-images/) . In this example .RKE will use `registry.com` as the default registry for all system images, e.g. `rancher/rke-tools:v0.1.14` will become `registry.com/rancher/rke-tools:v0.1.14`. As of v0.1.10, RKE supports specifying a default registry from the list of private registries to be used with all [system images](../../config-options/system-images/system-images.md). In this example, RKE will use `registry.com` as the default registry for all system images, e.g. `rancher/rke-tools:v0.1.14` will become `registry.com/rancher/rke-tools:v0.1.14`.
```yaml ```yaml
private_registries: private_registries:
@ -45,11 +45,11 @@ private_registries:
### Air-gapped Setups ### Air-gapped Setups
By default, all system images are being pulled from DockerHub. If you are on a system that does not have access to DockerHub, you will need to create a private registry that is populated with all the required [system images](config-options/system-images/). By default, all system images are being pulled from DockerHub. If you are on a system that does not have access to DockerHub, you will need to create a private registry that is populated with all the required [system images](../../config-options/system-images/system-images.md).
As of v0.1.10, you have to configure your private registry credentials, but you can specify this registry as a default registry so that all [system images](config-options/system-images/) are pulled from the designated private registry. You can use the command `rke config --system-images` to get the list of default system images to populate your private registry. As of v0.1.10, you have to configure your private registry credentials, but you can specify this registry as a default registry so that all [system images](../../config-options/system-images/system-images.md) are pulled from the designated private registry. You can use the command `rke config --system-images` to get the list of default system images to populate your private registry.
Before v0.1.10, you had to configure your private registry credentials **and** update the names of all the [system images](config-options/system-images/) in the `cluster.yml` so that the image names would have the private registry URL appended before each image name. Before v0.1.10, you had to configure your private registry credentials **and** update the names of all the [system images](../../config-options/system-images/system-images.md) in the `cluster.yml` so that the image names would have the private registry URL appended before each image name.
### Amazon Elastic Container Registry (ECR) Private Registry Setup ### Amazon Elastic Container Registry (ECR) Private Registry Setup

4
docs/config-options/system-images/system-images.md
View File

@ -5,7 +5,7 @@ When RKE is deploying Kubernetes, there are several images that are pulled. Thes
As of `v0.1.6`, the functionality of a couple of the system images were consolidated into a single `rancher/rke-tools` image to simplify and speed the deployment process. As of `v0.1.6`, the functionality of a couple of the system images were consolidated into a single `rancher/rke-tools` image to simplify and speed the deployment process.
You can configure the [network plug-ins](config-options/add-ons/network-plugins/), [ingress controller](config-options/add-ons/ingress-controllers/) and [dns provider](config-options/add-ons/dns/) as well as the options for these add-ons separately in the `cluster.yml`. You can configure the [network plug-ins](../add-ons/network-plugins/network-plugins.md), [ingress controller](../add-ons/ingress-controllers/ingress-controllers.md) and [dns provider](../add-ons/dns/dns.md) as well as the options for these add-ons separately in the `cluster.yml`.
Below is an example of the list of system images used to deploy Kubernetes through RKE. The default versions of Kubernetes are tied to specific versions of system images. Below is an example of the list of system images used to deploy Kubernetes through RKE. The default versions of Kubernetes are tied to specific versions of system images.
@ -78,4 +78,4 @@ system_images:
### Air-gapped Setups ### Air-gapped Setups
If you have an air-gapped setup and cannot access `docker.io`, you will need to set up your [private registry](config-options/private-registries/) in your cluster configuration file. After you set up private registry, you will need to update these images to pull from your private registry. If you have an air-gapped setup and cannot access `docker.io`, you will need to set up your [private registry](../private-registries/private-registries.md) in your cluster configuration file. After you set up private registry, you will need to update these images to pull from your private registry.

4
docs/os/os.md
View File

@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
RKE runs on almost any Linux OS with Docker installed. For details on which OS and Docker versions were tested with each version, refer to the [support matrix](https://www.suse.com/suse-rke1/support-matrix/all-supported-versions/). RKE runs on almost any Linux OS with Docker installed. For details on which OS and Docker versions were tested with each version, refer to the [support matrix](https://www.suse.com/suse-rke1/support-matrix/all-supported-versions/).
- [SSH user](config-options/nodes/#ssh-user) - The SSH user used for node access must be a member of the `docker` group on the node: - [SSH user](../config-options/nodes/nodes.md#ssh-users) - The SSH user used for node access must be a member of the `docker` group on the node:
``` ```
usermod -aG docker <user_name> usermod -aG docker <user_name>
@ -121,7 +121,7 @@ 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/nodes.md#ssh-users) 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 :::note

2
docs/upgrades/how-upgrades-work/how-upgrades-work.md
View File

@ -58,7 +58,7 @@ RKE will handle all worker node upgrades before upgrading any add-ons. As long a
### Upgrades of Addons ### Upgrades of Addons
The availability of your applications partly depends on the availability of [RKE addons.](config-options/add-ons/) Addons are used to deploy several cluster components, including network plug-ins, the Ingress controller, DNS provider, and metrics server. The availability of your applications partly depends on the availability of [RKE addons.](../../config-options/add-ons/add-ons.md) Addons are used to deploy several cluster components, including network plug-ins, the Ingress controller, DNS provider, and metrics server.
Because RKE addons are necessary for allowing traffic into the cluster, they will need to be updated in batches to maintain availability. You will need to configure the maximum number of unavailable replicas for each addon in the `cluster.yml` to ensure that your cluster will retain enough available replicas during an upgrade. Because RKE addons are necessary for allowing traffic into the cluster, they will need to be updated in batches to maintain availability. You will need to configure the maximum number of unavailable replicas for each addon in the `cluster.yml` to ensure that your cluster will retain enough available replicas during an upgrade.