mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-26 13:08:11 +00:00
Globally import Tabs and TabItem
This commit is contained in:
-3
@@ -2,9 +2,6 @@
|
||||
title: EC2 Node Template Configuration
|
||||
---
|
||||
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
|
||||
For more details about EC2, nodes, refer to the official documentation for the [EC2 Management Console](https://aws.amazon.com/ec2).
|
||||
|
||||
<Tabs>
|
||||
|
||||
-3
@@ -2,9 +2,6 @@
|
||||
title: Azure Node Template Configuration
|
||||
---
|
||||
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
|
||||
For more information about Azure, refer to the official [Azure documentation.](https://docs.microsoft.com/en-us/azure/?product=featured)
|
||||
|
||||
<Tabs>
|
||||
|
||||
-3
@@ -2,9 +2,6 @@
|
||||
title: DigitalOcean Node Template Configuration
|
||||
---
|
||||
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
|
||||
<Tabs>
|
||||
<TabItem value="Rancher v2.2.0+">
|
||||
|
||||
|
||||
-1
@@ -2,7 +2,6 @@
|
||||
title: vSphere Node Template Configuration in Rancher before v2.0.4
|
||||
---
|
||||
|
||||
|
||||
## Account Access
|
||||
In the **Account Access** section, enter the vCenter FQDN or IP address and the credentials for the vSphere user account.
|
||||
|
||||
|
||||
-1
@@ -2,7 +2,6 @@
|
||||
title: vSphere Node Template Configuration in Rancher v2.0.4
|
||||
---
|
||||
|
||||
|
||||
## Account Access
|
||||
In the **Account Access** section, enter the vCenter FQDN or IP address and the credentials for the vSphere user account.
|
||||
|
||||
|
||||
-1
@@ -2,7 +2,6 @@
|
||||
title: vSphere Node Template Configuration in Rancher v2.2.0
|
||||
---
|
||||
|
||||
|
||||
## Account Access
|
||||
|
||||
| Parameter | Required | Description |
|
||||
|
||||
-1
@@ -2,7 +2,6 @@
|
||||
title: vSphere Node Template Configuration in Rancher v2.3.3
|
||||
---
|
||||
|
||||
|
||||
## Account Access
|
||||
|
||||
| Parameter | Required | Description |
|
||||
|
||||
@@ -2,9 +2,6 @@
|
||||
title: Configuring Persistent Data for Pipeline Components
|
||||
---
|
||||
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
|
||||
The pipelines' internal Docker registry and the Minio workloads use ephemeral volumes by default. This default storage works out-of-the-box and makes testing easy, but you lose the build images and build logs if the node running the Docker Registry or Minio fails. In most cases this is fine. If you want build images and logs to survive node failures, you can configure the Docker Registry and Minio to use persistent volumes.
|
||||
|
||||
This section assumes that you understand how persistent storage works in Kubernetes. For more information, refer to the section on [how storage works.](../../how-to-guides/advanced-user-guides/manage-clusters/create-kubernetes-persistent-storage/manage-persistent-storage/about-persistent-storage.md)
|
||||
|
||||
Reference in New Issue
Block a user