public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 20:48:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updating tabs

Browse Source
This commit is contained in:
Jennifer Travinski
2022-07-14 14:40:53 -04:00
parent e0b784ad21
commit d7eb4f8378
122 changed files with 876 additions and 876 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/v2.5/en/installation/resources/choosing-version/choosing-version.md
+6 -6
View File
@@ -16,8 +16,8 @@ The Helm chart version also applies to RancherD installs because RancherD instal
> **Note:** RancherD was an experimental feature available as part of Rancher v2.5.4 through v2.5.10 but is now deprecated and not available for recent releases.
{{% tabs %}}
{{% tab "Helm Charts" %}}
<Tabs>
<TabItem label="Helm Charts">
When installing, upgrading, or rolling back Rancher Server when it is [installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.5/en/installation/install-rancher-on-k8s/), Rancher server is installed using a Helm chart on a Kubernetes cluster. Therefore, as you prepare to install or upgrade a high availability Rancher configuration, you must add a Helm chart repository that contains the charts for installing Rancher.
@@ -80,8 +80,8 @@ After installing Rancher, if you want to change which Helm chart repository to i
```
4. Continue to follow the steps to [upgrade Rancher]({{<baseurl>}}/rancher/v2.5/en/installation/upgrades-rollbacks/upgrades/ha) from the new Helm chart repository.
{{% /tab %}}
{{% tab "Docker Images" %}}
</TabItem>
<TabItem label="Docker Images">
When performing [Docker installs]({{<baseurl>}}/rancher/v2.5/en/installation/single-node), upgrades, or rollbacks, you can use _tags_ to install a specific version of Rancher.
### Server Tags
@@ -99,5 +99,5 @@ Rancher Server is distributed as a Docker image, which have tags attached to the
> - The `master` tag or any tag with `-rc` or another suffix is meant for the Rancher testing team to validate. You should not use these tags, as these builds are not officially supported.
> - Want to install an alpha review for preview? Install using one of the alpha tags listed on our [announcements page](https://forums.rancher.com/c/announcements) (e.g., `v2.2.0-alpha1`). Caveat: Alpha releases cannot be upgraded to or from any other release.
{{% /tab %}}
{{% /tabs %}}
</TabItem>
</Tabs>
versioned_docs/version-2.5/v2.5/en/installation/resources/feature-flags/feature-flags.md
+6 -6
View File
@@ -77,8 +77,8 @@ Here is an example of a command for passing in the feature flag names when rende
The Helm 3 command is as follows:
{{% tabs %}}
{{% tab "Rancher v2.5.8+" %}}
<Tabs>
<TabItem label="Rancher v2.5.8+">
```
helm template rancher ./rancher-<VERSION>.tgz --output-dir . \
@@ -92,8 +92,8 @@ helm template rancher ./rancher-<VERSION>.tgz --output-dir . \
--set 'extraEnv[0].name=CATTLE_FEATURES'
--set 'extraEnv[0].value=<FEATURE-FLAG-NAME-1>=true,<FEATURE-FLAG-NAME-2>=true'
```
{{% /tab %}}
{{% tab "Rancher before v2.5.8" %}}
</TabItem>
<TabItem label="Rancher before v2.5.8">
```
helm template rancher ./rancher-<VERSION>.tgz --output-dir . \
@@ -106,8 +106,8 @@ helm template rancher ./rancher-<VERSION>.tgz --output-dir . \
--set 'extraEnv[0].name=CATTLE_FEATURES'
--set 'extraEnv[0].value=<FEATURE-FLAG-NAME-1>=true,<FEATURE-FLAG-NAME-2>=true'
```
{{% /tab %}}
{{% /tabs %}}
</TabItem>
</Tabs>
The Helm 2 command is as follows: