Add version-2.7 docs

2026-05-05 04:33:18 +00:00 · 2023-06-05 10:54:11 -07:00
parent ae741d3b8b
commit 754bfdcab5
868 changed files with 136645 additions and 0 deletions
@@ -0,0 +1,13 @@
+---
+title: Continuous Delivery
+---
+
+As of Rancher v2.5, [Fleet](../../../how-to-guides/new-user-guides/deploy-apps-across-clusters/fleet.md) comes preinstalled in Rancher, and as of Rancher v2.6, Fleet can no longer be fully disabled. However, the Fleet feature for GitOps continuous delivery may be disabled using the `continuous-delivery` feature flag.
+
+To enable or disable this feature, refer to the instructions on [the main page about enabling experimental features.](../../../pages-for-subheaders/enable-experimental-features.md)
+
+Environment Variable Key | Default Value | Description
+---|---|---
+ `continuous-delivery` | `true` | This flag disables the GitOps continuous delivery feature of Fleet. |
+
+If Fleet was disabled in Rancher v2.5.x, it will become enabled if Rancher is upgraded to v2.6.x. Only the continuous delivery part of Fleet can be disabled. When `continuous-delivery` is disabled, the `gitjob` deployment is no longer deployed into the Rancher server's local cluster, and `continuous-delivery` is not shown in the Rancher UI.
@@ -0,0 +1,32 @@
+---
+title: UI for Istio Virtual Services and Destination Rules
+---
+
+This feature enables a UI that lets you create, read, update and delete virtual services and destination rules, which are traffic management features of Istio.
+
+> **Prerequisite:** Turning on this feature does not enable Istio. A cluster administrator needs to [enable Istio for the cluster](../../../pages-for-subheaders/istio-setup-guide.md) in order to use the feature.
+
+To enable or disable this feature, refer to the instructions on [the main page about enabling experimental features.](../../../pages-for-subheaders/enable-experimental-features.md)
+
+Environment Variable Key | Default Value | Status | Available as of
+---|---|---|---
+`istio-virtual-service-ui` |`false` |  Experimental | v2.3.0
+`istio-virtual-service-ui` | `true` | GA                    | v2.3.2
+
+## About this Feature
+
+A central advantage of Istio's traffic management features is that they allow dynamic request routing, which is useful for canary deployments, blue/green deployments, or A/B testing.
+
+When enabled, this feature turns on a page that lets you configure some traffic management features of Istio using the Rancher UI. Without this feature, you need to use `kubectl` to manage traffic with Istio.
+
+The feature enables two UI tabs: one tab for **Virtual Services** and another for **Destination Rules**.
+
+- **Virtual services** intercept and direct traffic to your Kubernetes services, allowing you to direct percentages of traffic from a request to different services. You can use them to define a set of routing rules to apply when a host is addressed. For details, refer to the [Istio documentation.](https://istio.io/docs/reference/config/networking/v1alpha3/virtual-service/)
+- **Destination rules** serve as the single source of truth about which service versions are available to receive traffic from virtual services. You can use these resources to define policies that apply to traffic that is intended for a service after routing has occurred. For details, refer to the [Istio documentation.](https://istio.io/docs/reference/config/networking/v1alpha3/destination-rule)
+
+To see these tabs,
+
+1.  Click **☰ > Cluster Management**.
+1. Go to the cluster where Istio is installed and click **Explore**.
+1. In the left navigation bar, click **Istio**.
+1. You will see tabs for **Kiali** and **Jaeger**. From the left navigation bar, you can view and configure **Virtual Services** and **Destination Rules**.
@@ -0,0 +1,45 @@
+---
+title: "Running on ARM64 (Experimental)"
+---
+
+:::caution
+
+Running on an ARM64 platform is currently an experimental feature and is not yet officially supported in Rancher. Therefore, we do not recommend using ARM64 based nodes in a production environment.
+
+:::
+
+The following options are available when using an ARM64 platform:
+
+- Running Rancher on ARM64 based node(s)
+  - Only for Docker Install. Please note that the following installation command replaces the examples found in the [Docker Install link](../../../pages-for-subheaders/rancher-on-a-single-node-with-docker.md):
+
+  ```
+  # In the last line `rancher/rancher:vX.Y.Z`, be certain to replace "X.Y.Z" with a released version in which ARM64 builds exist. For  example, if your matching version is v2.5.8, you would fill in this line with `rancher/rancher:v2.5.8`.
+  docker run -d --restart=unless-stopped \
+    -p 80:80 -p 443:443 \
+    --privileged \
+    rancher/rancher:vX.Y.Z
+  ```
+
+:::note
+
+To check if your specific released version is compatible with the ARM64 architecture, you may navigate to your
+version's release notes in the following two ways:
+
+- Manually find your version using https://github.com/rancher/rancher/releases.
+- Go directly to your version using the tag and the specific version number. If you plan to use v2.5.8, for example, you may navigate to https://github.com/rancher/rancher/releases/tag/v2.5.8.
+
+:::
+
+- Create custom cluster and adding ARM64 based node(s)
+  - Kubernetes cluster version must be 1.12 or higher
+  - CNI Network Provider must be [Flannel](../../../faq/container-network-interface-providers.md#flannel)
+- Importing clusters that contain ARM64 based nodes
+  - Kubernetes cluster version must be 1.12 or higher
+
+Please see [Cluster Options](cluster-provisioning/rke-clusters/options/) how to configure the cluster options.
+
+The following features are not tested:
+
+- Monitoring, alerts, notifiers, pipelines and logging
+- Launching apps from the catalog
@@ -0,0 +1,39 @@
+---
+title: Allow Unsupported Storage Drivers
+---
+
+This feature allows you to use types for storage providers and provisioners that are not enabled by default.
+
+To enable or disable this feature, refer to the instructions on [the main page about enabling experimental features.](../../../pages-for-subheaders/enable-experimental-features.md)
+
+Environment Variable Key | Default Value | Description
+---|---|---
+ `unsupported-storage-drivers` | `false` | This feature enables types for storage providers and provisioners that are not enabled by default.
+
+### Types for Persistent Volume Plugins that are Enabled by Default
+Below is a list of storage types for persistent volume plugins that are enabled by default. When enabling this feature flag, any persistent volume plugins that are not on this list are considered experimental and unsupported:
+
+Name | Plugin
+--------|----------
+Amazon EBS Disk |  `aws-ebs`
+AzureFile | `azure-file`
+AzureDisk | `azure-disk`
+Google Persistent Disk | `gce-pd`
+Longhorn | `flex-volume-longhorn`
+VMware vSphere Volume |  `vsphere-volume`
+Local | `local`
+Network File System | `nfs`
+hostPath | `host-path`
+
+### Types for StorageClass that are Enabled by Default
+Below is a list of storage types for a StorageClass that are enabled by default. When enabling this feature flag, any persistent volume plugins that are not on this list are considered experimental and unsupported:
+
+Name | Plugin
+--------|--------
+Amazon EBS Disk |  `aws-ebs`
+AzureFile | `azure-file`
+AzureDisk | `azure-disk`
+Google Persistent Disk | `gce-pd`
+Longhorn | `flex-volume-longhorn`
+VMware vSphere Volume | `vsphere-volume`
+Local | `local`