mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 04:28:15 +00:00
Review airgap system-charts
This commit is contained in:
committed by
Denise
parent
4da6ab9d23
commit
f9925f28a8
+3
-3
@@ -6,11 +6,11 @@ aliases:
|
||||
|
||||
## A. Prepare System Charts
|
||||
|
||||
The [System Charts](https://github.com/rancher/system-charts) contains all the catalog items required for features such as moniotring, logging, alerting and global DNS. To keep these features working, you will need to make that the `rancher/rancher` container can either access `https://git.rancher.io/system-charts.git` or that you configure the system charts to be updated from your own mirrored Git repository.
|
||||
The [System Charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as moniotring, logging, alerting and global DNS. To be able to use these features in an air gap install, you will need to mirror the `system-charts` repository to a location in your network that Rancher can reach and configure Rancher to use that repository.
|
||||
|
||||
## B. Configure System Charts
|
||||
|
||||
Rancher needs to be configured to use the mirrored Git repository if the `rancher/rancher` container cannot access `https://git.rancher.io/system-charts.git`
|
||||
Rancher needs to be configured to use the Git mirror of the `system-charts` repository.
|
||||
|
||||
1. Log into Rancher.
|
||||
|
||||
@@ -18,7 +18,7 @@ Rancher needs to be configured to use the mirrored Git repository if the `ranche
|
||||
|
||||

|
||||
|
||||
1. Click **Edit** on the upper right corner and update the **url**.
|
||||
1. Click **Edit** on the upper right corner and update the value for **url** to the location of the Git mirror of the `system-charts` repository.
|
||||
|
||||

|
||||
|
||||
|
||||
+3
-3
@@ -6,11 +6,11 @@ aliases:
|
||||
|
||||
## A. Prepare System Charts
|
||||
|
||||
The [System Charts](https://github.com/rancher/system-charts) contains all the catalog items required for features such as moniotring, logging, alerting and global DNS. To keep these features working, you will need to make that the `rancher/rancher` container can either access `https://git.rancher.io/system-charts.git` or that you configure the system charts to be updated from your own mirrored Git repository.
|
||||
The [System Charts](https://github.com/rancher/system-charts) repository contains all the catalog items required for features such as moniotring, logging, alerting and global DNS. To be able to use these features in an air gap install, you will need to mirror the `system-charts` repository to a location in your network that Rancher can reach and configure Rancher to use that repository.
|
||||
|
||||
## B. Configure System Charts
|
||||
|
||||
Rancher needs to be configured to use the mirrored Git repository if the `rancher/rancher` container cannot access `https://git.rancher.io/system-charts.git`
|
||||
Rancher needs to be configured to use the Git mirror of the `system-charts` repository.
|
||||
|
||||
1. Log into Rancher.
|
||||
|
||||
@@ -18,7 +18,7 @@ Rancher needs to be configured to use the mirrored Git repository if the `ranche
|
||||
|
||||

|
||||
|
||||
1. Click **Edit** on the upper right corner and update the **url**.
|
||||
1. Click **Edit** on the upper right corner and update the value for **url** to the location of the Git mirror of the `system-charts` repository.
|
||||
|
||||

|
||||
|
||||
|
||||
@@ -24,11 +24,11 @@ The following instructions will guide you through upgrading a high-availability
|
||||
|
||||
[Install or update](https://docs.helm.sh/using_helm/#installing-helm) Helm to the latest version.
|
||||
|
||||
- **Upgrades to v2.0.7+ only: check system namespace locations**
|
||||
- **Upgrades to v2.0.7+ only: check system namespace locations**<br/>
|
||||
Starting in v2.0.7, Rancher introduced the `system` project, which is a project that's automatically created to store important namespaces that Kubernetes needs to operate. During upgrade to v2.0.7+, Rancher expects these namespaces to be unassigned from all projects. Before beginning upgrade, check your system namespaces to make sure that they're unassigned to [prevent cluster networking issues]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/namespace-migration/#preventing-cluster-networking-issues).
|
||||
|
||||
- **Upgrades to v2.2.0 only: make sure your own mirrored system charts up to date**
|
||||
Starting in v2.2.0, Rancher introduced the [System Charts](https://github.com/rancher/system-charts) contains all the catalog items required for features such as moniotring, logging, alerting and global DNS. During upgrade to v2.2.0, Rancher expects that the `rancher/rancher` container can either access `https://git.rancher.io/system-charts.git` or that you configure the system charts to be updated from your own mirrored Git repository. Follow the directions in Air Gap Installation to [configure Rancher system charts]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-high-availability/config-rancher-system-charts/) required for the new version of Rancher.
|
||||
- **Upgrades to v2.2.0 only: mirror system-charts repository and configure Rancher**<br/>
|
||||
Starting in v2.2.0, Rancher introduced the [System Charts](https://github.com/rancher/system-charts) repository which contains all the catalog items required for features such as monitoring, logging, alerting and global DNS. To be able to use these features in an air gap install, you will need to mirror the `system-charts` repository locally and configure Rancher to use that repository. Please follow the instructions to [configure Rancher system charts]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-high-availability/config-rancher-system-charts/).
|
||||
|
||||
## Caveats
|
||||
Upgrades _to_ or _from_ any chart in the [rancher-alpha repository]({{< baseurl >}}/rancher/v2.x/en/installation/server-tags/#helm-chart-repositories/) aren't supported.
|
||||
|
||||
@@ -9,7 +9,8 @@ To upgrade an air gapped Rancher Server, update your private registry with the l
|
||||
## Prerequisites
|
||||
**Upgrades to v2.0.7+ only:** Starting in v2.0.7, Rancher introduced the `system` project, which is a project that's automatically created to store important namespaces that Kubernetes needs to operate. During upgrade to v2.0.7+, Rancher expects these namespaces to be unassigned from all projects. Before beginning upgrade, check your system namespaces to make sure that they're unassigned to [prevent cluster networking issues]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/namespace-migration/#preventing-cluster-networking-issues).
|
||||
|
||||
**Upgrades to v2.2.0 only:** Starting in v2.2.0, Rancher introduced the [System Charts](https://github.com/rancher/system-charts) contains all the catalog items required for features such as moniotring, logging, alerting and global DNS. During upgrade to v2.2.0, Rancher expects that the `rancher/rancher` container can either access `https://git.rancher.io/system-charts.git` or that you configure the system charts to be updated from your own mirrored Git repository. Follow the directions in Air Gap Installation to [configure Rancher system charts]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-single-node/config-rancher-system-charts/) required for the new version of Rancher.
|
||||
**Upgrades to v2.2.0 only: mirror system-charts repository and configure Rancher**<br/>
|
||||
Starting in v2.2.0, Rancher introduced the [System Charts](https://github.com/rancher/system-charts) repository which contains all the catalog items required for features such as monitoring, logging, alerting and global DNS. To be able to use these features in an air gap install, you will need to mirror the `system-charts` repository locally and configure Rancher to use that repository. Please follow the instructions to [configure Rancher system charts]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-single-node/config-rancher-system-charts/).
|
||||
|
||||
## Caveats
|
||||
Upgrades _to_ or _from_ any tag containing [alpha]({{< baseurl >}}/rancher/v2.x/en/installation/server-tags/#server-tags) aren't supported.
|
||||
|
||||
Reference in New Issue
Block a user