mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 20:48:11 +00:00
Fix tables of contents, headers and formatting
This commit is contained in:
Catherine Luse
+6
-12
@@ -3,14 +3,8 @@ title: Nutanix Node Template Configuration
|
||||
weight: 2
|
||||
---
|
||||
|
||||
- [Account Access](#account-access)
|
||||
- [Scheduling](#scheduling)
|
||||
- [Instance Options](#instance-options)
|
||||
- [Networks](#networks)
|
||||
- [VM Categories](#vm-categories)
|
||||
- [cloud-init](#cloud-init)
|
||||
|
||||
# Account Access
|
||||
## Account Access
|
||||
|
||||
| Parameter | Required | Description | Default
|
||||
|:-----------------------------|:--------:|:-----------------------------------------------------------------|:-----
|
||||
@@ -19,7 +13,7 @@ weight: 2
|
||||
| Password | ✓ | Password of the Prism Central user |
|
||||
| Allow insecure communication | | Set to true to allow insecure SSL communication to Prism Central | False
|
||||
|
||||
# Scheduling
|
||||
## Scheduling
|
||||
|
||||
Choose what Nutanix cluster the virtual machine will be scheduled to.
|
||||
|
||||
@@ -27,7 +21,7 @@ Choose what Nutanix cluster the virtual machine will be scheduled to.
|
||||
|:----------|:--------:|:----------------------------------------------------------------------------
|
||||
| Cluster | ✓ | Name of the Nutanix cluster where the VM should be deployed (case sensitive)
|
||||
|
||||
# Instance Options
|
||||
## Instance Options
|
||||
|
||||
In the **Instance Options** section, configure the number of vCPUs, memory, and disk size for the VMs created by this template.
|
||||
|
||||
@@ -45,15 +39,15 @@ In the **Instance Options** section, configure the number of vCPUs, memory, and
|
||||
|
||||
The VM may use any modern Linux operating system that is configured with support for [cloud-init](https://cloudinit.readthedocs.io/en/latest/) using the [Config Drive v2 datasource](https://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html).
|
||||
|
||||
# Networks
|
||||
## Networks
|
||||
|
||||
The node template allows a VM to be provisioned with multiple networks. In the **Network** field, you can click **Add** to add any networks available to you in AOS.
|
||||
|
||||
# VM Categories
|
||||
## VM Categories
|
||||
|
||||
A category is a grouping of entities into a key value pair. Typically, VMs are assigned to a category based on some criteria. Policies can then be tied to those entities that are assigned (grouped by) a specific category value.
|
||||
|
||||
# cloud-init
|
||||
## cloud-init
|
||||
|
||||
[Cloud-init](https://cloudinit.readthedocs.io/en/latest/) allows you to initialize your nodes by applying configuration on the first boot. This may involve things such as creating users or authorizing SSH keys.
|
||||
|
||||
|
||||
+6
-12
@@ -3,14 +3,8 @@ title: VSphere Node Template Configuration
|
||||
weight: 2
|
||||
---
|
||||
|
||||
- [Account Access](#account-access)
|
||||
- [Scheduling](#scheduling)
|
||||
- [Instance Options](#instance-options)
|
||||
- [Networks](#networks)
|
||||
- [Node tags and custom attributes](#node-tags-and-custom-attributes)
|
||||
- [cloud-init](#cloud-init)
|
||||
|
||||
# Account Access
|
||||
## Account Access
|
||||
|
||||
| Parameter | Required | Description |
|
||||
|:----------------------|:--------:|:-----|
|
||||
@@ -24,7 +18,7 @@ Your cloud credential has these fields:
|
||||
| Port | Optional: configure configure the port of the vCenter or ESXi server. |
|
||||
| Username and password | Enter your vSphere login username and password. |
|
||||
|
||||
# Scheduling
|
||||
## Scheduling
|
||||
|
||||
Choose what hypervisor the virtual machine will be scheduled to.
|
||||
|
||||
@@ -38,7 +32,7 @@ The fields in the **Scheduling** section should auto-populate with the data cent
|
||||
| Folder | | Name of a folder in the datacenter to create the VMs in. Must already exist. The VM folders in this dropdown menu directly correspond to your VM folders in vSphere. The folder name should be prefaced with `vm/` in your vSphere config file. |
|
||||
| Host | | The IP of the host system to schedule VMs in. Leave this field blank for a standalone ESXi or for a cluster with DRS (Distributed Resource Scheduler). If specified, the host system's pool will be used and the **Resource Pool** parameter will be ignored. |
|
||||
|
||||
# Instance Options
|
||||
## Instance Options
|
||||
|
||||
In the **Instance Options** section, configure the number of vCPUs, memory, and disk size for the VMs created by this template.
|
||||
|
||||
@@ -66,11 +60,11 @@ Choose the way that the VM will be created:
|
||||
- **Clone an existing virtual machine:** In the **Virtual machine** field, choose an existing VM that the new VM will be cloned from.
|
||||
- **Install from boot2docker ISO:** Ensure that the **OS ISO URL** field contains the URL of a VMware ISO release for RancherOS (`rancheros-vmware.iso`). Note that this URL must be accessible from the nodes running your Rancher server installation.
|
||||
|
||||
# Networks
|
||||
## Networks
|
||||
|
||||
The node template now allows a VM to be provisioned with multiple networks. In the **Networks** field, you can now click **Add Network** to add any networks available to you in vSphere.
|
||||
|
||||
# Node Tags and Custom Attributes
|
||||
## Node Tags and Custom Attributes
|
||||
|
||||
Tags allow you to attach metadata to objects in the vSphere inventory to make it easier to sort and search for these objects.
|
||||
|
||||
@@ -84,7 +78,7 @@ Custom attributes are a legacy feature that will eventually be removed from vSph
|
||||
|
||||
:::
|
||||
|
||||
# cloud-init
|
||||
## cloud-init
|
||||
|
||||
[Cloud-init](https://cloudinit.readthedocs.io/en/latest/) allows you to initialize your nodes by applying configuration on the first boot. This may involve things such as creating users, authorizing SSH keys or setting up the network.
|
||||
|
||||
|
||||
+8
-8
@@ -4,20 +4,20 @@ title: AKS Cluster Configuration Reference
|
||||
weight: 4
|
||||
---
|
||||
|
||||
# Changes in Rancher v2.6
|
||||
## Changes in Rancher v2.6
|
||||
|
||||
- Support for adding more than one node pool
|
||||
- Support for private clusters
|
||||
- Enabled autoscaling node pools
|
||||
- The AKS permissions are now configured in cloud credentials
|
||||
|
||||
# Role-based Access Control
|
||||
## Role-based Access Control
|
||||
|
||||
When provisioning an AKS cluster in the Rancher UI, RBAC cannot be disabled. If role-based access control is disabled for the cluster in AKS, the cluster cannot be registered or imported into Rancher.
|
||||
|
||||
Rancher can configure member roles for AKS clusters in the same way as any other cluster. For more information, see the section on [role-based access control.](../../../pages-for-subheaders/manage-role-based-access-control-rbac.md)
|
||||
|
||||
# Cloud Credentials
|
||||
## Cloud Credentials
|
||||
|
||||
:::note
|
||||
|
||||
@@ -50,19 +50,19 @@ Microsoft provides multiple [clouds](https://docs.microsoft.com/en-us/cli/azure/
|
||||
- AzureChinaCloud
|
||||
- AzureUSGovernmentCloud
|
||||
|
||||
# Account Access
|
||||
## Account Access
|
||||
|
||||
In this section you will need to select an existing Azure cloud credential or create a new one.
|
||||
|
||||
For help configuring your Azure cloud credential, see [this section.](#cloud-credentials)
|
||||
|
||||
# Cluster Location
|
||||
## Cluster Location
|
||||
|
||||
Configure the cluster and node location. For more information on availability zones for AKS, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/availability-zones)
|
||||
|
||||
The high availability locations include multiple availability zones.
|
||||
|
||||
# Cluster Options
|
||||
## Cluster Options
|
||||
|
||||
### Kubernetes Version
|
||||
|
||||
@@ -92,7 +92,7 @@ The key used to create an SSH connection to the Linux nodes.
|
||||
|
||||
Cluster tags can be useful if your organization uses tags as a way to organize resources across multiple Azure services. These tags don't apply to resources within the cluster.
|
||||
|
||||
# Networking Options
|
||||
## Networking Options
|
||||
|
||||
### LoadBalancer SKU
|
||||
|
||||
@@ -177,7 +177,7 @@ Please be aware that when registering an existing AKS cluster, the cluster might
|
||||
|
||||
For more information about connecting to an AKS private cluster, see the [AKS documentation.](https://docs.microsoft.com/en-us/azure/aks/private-clusters#options-for-connecting-to-the-private-cluster)
|
||||
|
||||
# Node Pools
|
||||
## Node Pools
|
||||
|
||||
### Mode
|
||||
|
||||
|
||||
+3
-3
@@ -6,14 +6,14 @@ weight: 6
|
||||
|
||||
This section covers the configuration options that are available in Rancher for a new or existing K3s Kubernetes cluster.
|
||||
|
||||
# Overview
|
||||
## Overview
|
||||
|
||||
You can configure the Kubernetes options one of two ways:
|
||||
|
||||
- [Rancher UI](#configuration-options-in-the-rancher-ui): Use the Rancher UI to select options that are commonly customized when setting up a Kubernetes cluster.
|
||||
- [Cluster Config File](#cluster-config-file): Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create a K3s config file. Using a config file allows you to set any of the [options](https://rancher.com/docs/k3s/latest/en/installation/install-options/) available in an K3s installation.
|
||||
|
||||
# Configuration Options in the Rancher UI
|
||||
## Configuration Options in the Rancher UI
|
||||
|
||||
:::tip
|
||||
|
||||
@@ -138,7 +138,7 @@ Option to remove all pods from the node prior to upgrading.
|
||||
|
||||
Option to set kubelet options for different nodes. For available options, refer to the [Kubernetes documentation](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/).
|
||||
|
||||
# Cluster Config File
|
||||
## Cluster Config File
|
||||
|
||||
Instead of using the Rancher UI forms to choose Kubernetes options for the cluster, advanced users can create an K3s config file. Using a config file allows you to set any of the [options](https://rancher.com/docs/k3s/latest/en/installation/install-options/) available in an K3s installation.
|
||||
|
||||
|
||||
+6
-36
@@ -8,38 +8,8 @@ When Rancher installs Kubernetes, it uses [RKE](../../../pages-for-subheaders/la
|
||||
|
||||
This section covers the configuration options that are available in Rancher for a new or existing RKE Kubernetes cluster.
|
||||
|
||||
- [Overview](#overview)
|
||||
- [Editing Clusters with a Form in the Rancher UI](#editing-clusters-with-a-form-in-the-rancher-ui)
|
||||
- [Editing Clusters with YAML](#editing-clusters-with-yaml)
|
||||
- [Configuration Options in the Rancher UI](#configuration-options-in-the-rancher-ui)
|
||||
- [Kubernetes Version](#kubernetes-version)
|
||||
- [Network Provider](#network-provider)
|
||||
- [Project Network Isolation](#project-network-isolation)
|
||||
- [Kubernetes Cloud Providers](#kubernetes-cloud-providers)
|
||||
- [Private Registries](#private-registries)
|
||||
- [Authorized Cluster Endpoint](#authorized-cluster-endpoint)
|
||||
- [Node Pools](#node-pools)
|
||||
- [NGINX Ingress](#nginx-ingress)
|
||||
- [Metrics Server Monitoring](#metrics-server-monitoring)
|
||||
- [Pod Security Policy Support](#pod-security-policy-support)
|
||||
- [Docker Version on Nodes](#docker-version-on-nodes)
|
||||
- [Docker Root Directory](#docker-root-directory)
|
||||
- [Default Pod Security Policy](#default-pod-security-policy)
|
||||
- [Node Port Range](#node-port-range)
|
||||
- [Recurring etcd Snapshots](#recurring-etcd-snapshots)
|
||||
- [Agent Environment Variables](#agent-environment-variables)
|
||||
- [Updating ingress-nginx](#updating-ingress-nginx)
|
||||
- [RKE Cluster Config File Reference](#rke-cluster-config-file-reference)
|
||||
- [Config File Structure in Rancher](#config-file-structure-in-rancher)
|
||||
- [Default DNS Provider](#default-dns-provider)
|
||||
- [Rancher Specific Parameters in YAML](#rancher-specific-parameters-in-yaml)
|
||||
- [docker_root_dir](#docker_root_dir)
|
||||
- [enable_cluster_monitoring](#enable_cluster_monitoring)
|
||||
- [enable_network_policy](#enable_network_policy)
|
||||
- [local_cluster_auth_endpoint](#local_cluster_auth_endpoint)
|
||||
- [Custom Network Plug-in](#custom-network-plug-in)
|
||||
|
||||
# Overview
|
||||
## Overview
|
||||
|
||||
You can configure the Kubernetes options one of two ways:
|
||||
|
||||
@@ -54,7 +24,7 @@ For an example of RKE config file syntax, see the [RKE documentation](https://ra
|
||||
|
||||
The forms in the Rancher UI don't include all advanced options for configuring RKE. For the complete reference of configurable options for RKE Kubernetes clusters in YAML, see the [RKE documentation.](https://rancher.com/docs/rke/latest/en/config-options/)
|
||||
|
||||
# Editing Clusters with a Form in the Rancher UI
|
||||
## Editing Clusters with a Form in the Rancher UI
|
||||
|
||||
To edit your cluster,
|
||||
|
||||
@@ -62,7 +32,7 @@ To edit your cluster,
|
||||
1. Go to the cluster you want to configure and click **⋮ > Edit Config**.
|
||||
|
||||
|
||||
# Editing Clusters with YAML
|
||||
## Editing Clusters with YAML
|
||||
|
||||
Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE config file. Using a config file allows you to set any of the options available in an RKE installation, except for system_images configuration, by specifying them in YAML.
|
||||
|
||||
@@ -75,7 +45,7 @@ To edit an RKE config file directly from the Rancher UI,
|
||||
1. In the configuration form, scroll down and click **Edit as YAML**.
|
||||
1. Edit the RKE options under the `rancher_kubernetes_engine_config` directive.
|
||||
|
||||
# Configuration Options in the Rancher UI
|
||||
## Configuration Options in the Rancher UI
|
||||
|
||||
:::tip
|
||||
|
||||
@@ -217,7 +187,7 @@ If the `updateStrategy` of `ingress-nginx` is `OnDelete`, you will need to delet
|
||||
|
||||
|
||||
|
||||
# RKE Cluster Config File Reference
|
||||
## RKE Cluster Config File Reference
|
||||
|
||||
Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE config file. Using a config file allows you to set any of the [options available](https://rancher.com/docs/rke/latest/en/config-options/) in an RKE installation, except for `system_images` configuration. The `system_images` option is not supported when creating a cluster with the Rancher UI or API.
|
||||
|
||||
@@ -332,7 +302,7 @@ The table below indicates what DNS provider is deployed by default. See [RKE doc
|
||||
| v2.2.5 and higher | v1.13.x and lower | kube-dns |
|
||||
| v2.2.4 and lower | any | kube-dns |
|
||||
|
||||
# Rancher Specific Parameters in YAML
|
||||
## Rancher Specific Parameters in YAML
|
||||
|
||||
Besides the RKE config file options, there are also Rancher specific settings that can be configured in the Config File (YAML):
|
||||
|
||||
|
||||
+4
-4
@@ -6,21 +6,21 @@ weight: 5
|
||||
|
||||
This section covers the configuration options that are available in Rancher for a new or existing RKE2 Kubernetes cluster.
|
||||
|
||||
# Overview
|
||||
## Overview
|
||||
|
||||
You can configure the Kubernetes options in one of the two following ways:
|
||||
|
||||
- [Rancher UI](#configuration-options-in-the-rancher-ui): Use the Rancher UI to select options that are commonly customized when setting up a Kubernetes cluster.
|
||||
- [Cluster Config File](#cluster-config-file): Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE2 config file. Using a config file allows you to set many additional [options](https://docs.rke2.io/install/install_options/install_options) available for an RKE2 installation.
|
||||
|
||||
# Editing Clusters with a Form in the Rancher UI
|
||||
## Editing Clusters with a Form in the Rancher UI
|
||||
|
||||
To edit your cluster,
|
||||
|
||||
1. In the upper left corner, click **☰ > Cluster Management**.
|
||||
1. Go to the cluster you want to configure and click **⋮ > Edit Config**.
|
||||
|
||||
# Editing Clusters with YAML
|
||||
## Editing Clusters with YAML
|
||||
|
||||
Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE2 config file. Using a config file allows you to set any of the options available in an RKE2 installation by specifying them in YAML.
|
||||
|
||||
@@ -30,7 +30,7 @@ To edit an RKE2 config file directly from the Rancher UI,
|
||||
1. Go to the cluster you want to configure and click **⋮ > Edit as YAML**.
|
||||
1. Edit the RKE options under the `rkeConfig` directive.
|
||||
|
||||
# Configuration Options in the Rancher UI
|
||||
## Configuration Options in the Rancher UI
|
||||
|
||||
:::tip
|
||||
|
||||
|
||||
Reference in New Issue
Block a user