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

Convert accordion Hugo shortcode to <details> tag

Browse Source
This commit is contained in:
Billy Tat committed 2022-07-18 20:43:02 -07:00
1 parent 5dc3b086e0
commit 97f8fd1c09
70 files changed
+2731 -2344
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/en/installation/other-installation-methods/single-node-docker/single-node-upgrades/single-node-upgrades.md
+21 -14
View File
@@ -144,7 +144,8 @@ Select which option you had installed Rancher server
### Option A: Default Self-Signed Certificate
{{% accordion id="option-a" label="Click to expand" %}}
<details id="option-a">
<summary>Click to expand</summary>
If you have selected to use the Rancher generated self-signed certificate, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container.
@@ -162,11 +163,12 @@ docker run -d --volumes-from rancher-data \
Privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
{{% /accordion %}}
</details>
### Option B: Bring Your Own Certificate: Self-Signed
{{% accordion id="option-b" label="Click to expand" %}}
<details id="option-b">
<summary>Click to expand</summary>
If you have selected to bring your own self-signed certificate, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to have access to the same certificate that you had originally installed with.
@@ -197,11 +199,12 @@ docker run -d --volumes-from rancher-data \
Privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
{{% /accordion %}}
</details>
### Option C: Bring Your Own Certificate: Signed by Recognized CA
{{% accordion id="option-c" label="Click to expand" %}}
<details id="option-c">
<summary>Click to expand</summary>
If you have selected to use a certificate signed by a recognized CA, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to have access to the same certificates that you had originally installed with. Remember to include `--no-cacerts` as an argument to the container to disable the default CA certificate generated by Rancher.
@@ -230,11 +233,12 @@ docker run -d --volumes-from rancher-data \
```
Privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
{{% /accordion %}}
</details>
### Option D: Let's Encrypt Certificate
{{% accordion id="option-d" label="Click to expand" %}}
<details id="option-d">
<summary>Click to expand</summary>
:::caution
@@ -267,7 +271,7 @@ docker run -d --volumes-from rancher-data \
Privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
{{% /accordion %}}
</details>
</TabItem>
<TabItem value="Docker Air Gap Upgrade">
@@ -278,7 +282,8 @@ When starting the new Rancher server container, choose from the following option
### Option A: Default Self-Signed Certificate
{{% accordion id="option-a" label="Click to expand" %}}
<details id="option-a">
<summary>Click to expand</summary>
If you have selected to use the Rancher generated self-signed certificate, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container.
@@ -298,11 +303,12 @@ Placeholder | Description
```
Privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
{{% /accordion %}}
</details>
### Option B: Bring Your Own Certificate: Self-Signed
{{% accordion id="option-b" label="Click to expand" %}}
<details id="option-b">
<summary>Click to expand</summary>
If you have selected to bring your own self-signed certificate, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to have access to the same certificate that you had originally installed with.
@@ -333,11 +339,12 @@ docker run -d --restart=unless-stopped \
<REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher:<RANCHER_VERSION_TAG>
```
Privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
{{% /accordion %}}
</details>
### Option C: Bring Your Own Certificate: Signed by Recognized CA
{{% accordion id="option-c" label="Click to expand" %}}
<details id="option-c">
<summary>Click to expand</summary>
If you have selected to use a certificate signed by a recognized CA, you add the `--volumes-from rancher-data` to the command that you had started your original Rancher server container and need to have access to the same certificates that you had originally installed with.
@@ -374,7 +381,7 @@ docker run -d --volumes-from rancher-data \
<REGISTRY.YOURDOMAIN.COM:PORT>/rancher/rancher:<RANCHER_VERSION_TAG>
```
privileged access is [required.]({{<baseurl>}}/rancher/v2.6/en/installation/other-installation-methods/single-node-docker/#privileged-access-for-rancher)
{{% /accordion %}}
</details>
</TabItem>
</Tabs>