Merge branch 'main' into landing-page-longhorn

2026-09-26 13:08:11 +00:00 · 2023-10-19 11:00:10 -07:00
parent 78c1a71864 3c40971c1d
commit 6491999059
58 changed files with 3133 additions and 2428 deletions
@@ -20,7 +20,7 @@ The following is a list of feature flags available in Rancher. If you've upgrade

 - `continuous-delivery`: Allows Fleet GitOps to be disabled separately from Fleet. See [Continuous Delivery.](../../../how-to-guides/advanced-user-guides/enable-experimental-features/continuous-delivery.md) for more information.
 - `fleet`: The Rancher provisioning framework in v2.6 and later requires Fleet. The flag will be automatically enabled when you upgrade, even if you disabled this flag in an earlier version of Rancher. See [Fleet - GitOps at Scale](../../../how-to-guides/new-user-guides/deploy-apps-across-clusters/fleet.md) for more information.
- `harvester`: Manages access to the Virtualization Management page, where users can navigate directly to Harvester clusters and access the Harvester UI. See [Harvester Integration](../../../integrations-in-rancher/harvester.md) for more information.
+- `harvester`: Manages access to the Virtualization Management page, where users can navigate directly to Harvester clusters and access the Harvester UI. See [Harvester Integration Overview](../../../integrations-in-rancher/harvester/overview.md) for more information.
 - `istio-virtual-service-ui`: Enables a [visual interface](../../../how-to-guides/advanced-user-guides/enable-experimental-features/istio-traffic-management-features.md) to create, read, update, and delete Istio virtual services and destination rules, which are Istio traffic management features.
 - `legacy`: Enables a set of features from 2.5.x and earlier, that are slowly being phased out in favor of newer implementations. These are a mix of deprecated features as well as features that will eventually be available to newer versions. This flag is disabled by default on new Rancher installations. If you're upgrading from a previous version of Rancher, this flag is enabled.
 - `multi-cluster-management`: Allows multi-cluster provisioning and management of Kubernetes clusters. This flag can only be set at install time. It can't be enabled or disabled later.
@@ -196,7 +196,7 @@ If security isn't a large concern and you're okay with opening a few additional

 ### Ports for Harvester Clusters

-Refer [here](../../../integrations-in-rancher/harvester.md#port-requirements) for more information on Harvester port requirements.
+Refer to the [Harvester Integration Overview](../../../integrations-in-rancher/harvester/overview.md#port-requirements) for more information on Harvester port requirements.


 ### Ports for Rancher Launched Kubernetes Clusters using Node Pools
@@ -71,7 +71,7 @@ In a Kubernetes Install, if you elect to use the Rancher default self-signed TLS
    ```plain
    helm repo add jetstack https://charts.jetstack.io
    helm repo update
-    helm fetch jetstack/cert-manager --version v1.11.0
+    helm fetch jetstack/cert-manager
    helm template ./cert-manager-<version>.tgz | awk '$1 ~ /image:/ {print $2}' | sed s/\"//g >> ./rancher-images.txt
    ```

@@ -250,7 +250,7 @@ The workstation must have Docker 18.02+ in order to support manifests, which are
   ```plain
   helm repo add jetstack https://charts.jetstack.io
   helm repo update
-   helm fetch jetstack/cert-manager --version v1.11.0
+   helm fetch jetstack/cert-manager
   helm template ./cert-manager-<version>.tgz | awk '$1 ~ /image:/ {print $2}' | sed s/\"//g >> ./rancher-images.txt
   ```

@@ -35,7 +35,7 @@ kubectl create namespace cert-manager
 Install the CustomResourceDefinitions of cert-manager:

 ```
-kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.11.0/cert-manager.crds.yaml
+kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/<VERSION>/cert-manager.crds.yaml
 ```

 And install it with Helm. Note that cert-manager also needs your proxy configured in case it needs to communicate with Let's Encrypt or other external certificate issuers:
@@ -48,7 +48,7 @@ To see options on how to customize the cert-manager install (including for cases

 ```
 helm upgrade --install cert-manager jetstack/cert-manager \
-  --namespace cert-manager --version v1.11.0 \
+  --namespace cert-manager \
  --set http_proxy=http://${proxy_host} \
  --set https_proxy=http://${proxy_host} \
  --set no_proxy=127.0.0.0/8\\,10.0.0.0/8\\,cattle-system.svc\\,172.16.0.0/12\\,192.168.0.0/16\\,.svc\\,.cluster.local
@@ -6,6 +6,8 @@ title: Upgrading Cert-Manager
  <link rel="canonical" href="https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/upgrade-cert-manager"/>
 </head>

+Rancher is compatible with the API version cert-manager.io/v1 and was last tested with cert-manager version v1.13.1.
+
 Rancher uses cert-manager to automatically generate and renew TLS certificates for HA deployments of Rancher. As of Fall 2019, three important changes to cert-manager are set to occur that you need to take action on if you have an HA deployment of Rancher:

 1. [Let's Encrypt will be blocking cert-manager instances older than 0.8.0 starting November 1st 2019.](https://community.letsencrypt.org/t/blocking-old-cert-manager-versions/98753)
@@ -96,8 +98,7 @@ In order to upgrade cert-manager, follow these instructions:
    ```plain
    helm install \
      cert-manager jetstack/cert-manager \
-      --namespace cert-manager \
-      --version v1.11.0
+      --namespace cert-manager
    ```

 1. [Restore back up resources](https://cert-manager.io/docs/tutorials/backup/#restoring-resources)
@@ -129,7 +130,7 @@ Before you can perform the upgrade, you must prepare your air gapped environment
 1. Fetch the latest cert-manager chart available from the [Helm chart repository](https://artifacthub.io/packages/helm/cert-manager/cert-manager).

    ```plain
-    helm fetch jetstack/cert-manager --version v1.11.0
+    helm fetch jetstack/cert-manager
    ```

 1. Render the cert manager template with the options you would like to use to install the chart. Remember to set the `image.repository` option to pull the image from your private registry. This will create a `cert-manager` directory with the Kubernetes manifest files.
@@ -108,7 +108,7 @@ helm repo add rancher-latest https://releases.rancher.com/server-charts/latest

 kubectl create namespace cattle-system

-kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.11.0/cert-manager.crds.yaml
+kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/<VERSION>/cert-manager.crds.yaml

 helm repo add jetstack https://charts.jetstack.io

@@ -116,14 +116,12 @@ helm repo update

 helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager \
-  --create-namespace \
-  --version v1.11.0
+  --create-namespace

 # Windows Powershell
 helm install cert-manager jetstack/cert-manager `
  --namespace cert-manager `
-  --create-namespace `
-  --version v1.11.0
+  --create-namespace
 ```

 The final command to install Rancher is below. The command requires a domain name that forwards traffic to the Linux machine. For the sake of simplicity in this tutorial, you can use a fake domain name to create your proof-of-concept. An example of a fake domain name would be `<IP_OF_LINUX_NODE>.sslip.io`.
@@ -2,6 +2,8 @@
 title: Rancher Prime
 ---

-Rancher v2.7 introduces Rancher Prime, an evolution of the Rancher enterprise offering. Rancher Prime is a new edition of the commercial, enterprise offering built on the the same source code. Rancher’s product will therefore continue to be 100% open source with additional value coming in from security assurances, extended lifecycles, access to focused architectures and Kubernetes advisories. Rancher Prime will also offer options to get production support for innovative Rancher projects. With Rancher Prime, installation assets are hosted on a trusted registry owned and managed by Rancher.
+Prime is the Rancher ecosystem’s enterprise offering, with additional security, extended lifecycles, and access to Prime-exclusive documentation. Rancher Prime installation assets are hosted on a trusted SUSE registry, owned and managed by Rancher. The trusted Prime registry includes only stable releases that have been community-tested. 

-To get started with Rancher Prime, [go to this page](https://www.rancher.com/quick-start) and fill out the form.
+Prime also offers options for production support, as well as add-ons to your subscription that tailor to your commercial needs.
+
+To learn more and get started with Rancher Prime, please visit [this page](https://www.rancher.com/quick-start).
@@ -0,0 +1,11 @@
+---
+title: Virtualization on Kubernetes with Harvester
+---
+
+## Harvester
+
+Introduced in Rancher v2.6.1, Harvester is an open-source hyper-converged infrastructure (HCI) software built on Kubernetes. Harvester installs on bare metal servers and provides integrated virtualization and distributed storage capabilities. Although Harvester operates using Kubernetes, it does not require users to know Kubernetes concepts, making it a more user-friendly application.
+
+## Harvester with Rancher
+
+With Rancher Prime and Harvester, IT operators now have access to an enterprise-ready, simple-to-use infrastructure platform that cohesively manages their virtual machines and Kubernetes clusters alongside one another. For more information on the support offering, see the [Support Matrix](https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/harvester-v1-2-0/). With the Rancher Virtualization Management feature, users can import and manage multiple Harvester clusters. Leveraging the Rancher's authentication feature and RBAC control for multi-tenancy support.
@@ -1,5 +1,5 @@
 ---
-title: Harvester Integration
+title: Overview
 ---

 Introduced in Rancher v2.6.1, [Harvester](https://docs.harvesterhci.io/) is an open-source hyper-converged infrastructure (HCI) software built on Kubernetes. Harvester installs on bare metal servers and provides integrated virtualization and distributed storage capabilities. Although Harvester operates using Kubernetes, it does not require users to know Kubernetes concepts, making it a more user-friendly application.
@@ -36,13 +36,3 @@ In addition, other networking considerations are as follows:
 - Follow the networking setup guidance [here](https://docs.harvesterhci.io/v1.1/networking/clusternetwork).

 For other port requirements for other guest clusters, such as K3s and RKE1, please see [these docs](https://docs.harvesterhci.io/v1.1/install/requirements/#guest-clusters).
-
-### Limitations
-
---
-**Applicable to Rancher v2.6.1 and v2.6.2 only:**
-
- Harvester v0.3.0 doesn’t support air-gapped environment installation.
- Harvester v0.3.0 doesn’t support upgrade from v0.2.0 nor upgrade to v1.0.0.
-
---
@@ -0,0 +1,62 @@
+---
+title: Integrations in Rancher
+---
+import {Card, CardSection} from '@site/src/components/CardComponents';
+import {
+  ReadingModeMobileRegular, 
+  QuestionRegular, 
+  ArrowUpRegular,
+  PlayRegular,
+  FlowchartRegular,
+  RocketRegular
+} from '@fluentui/react-icons';
+import { FaAws, FaGoogle, FaCloud, FaServer, faGear } from "react-icons/fa6";
+import HarvesterIcon from '@site/static/img/harvester_logo_horizontal.svg';
+
+Prime is the Rancher ecosystem’s enterprise offering, with additional security, extended lifecycles, and access to Prime-exclusive documentation. Rancher Prime installation assets are hosted on a trusted SUSE registry, owned and managed by Rancher. The trusted Prime registry includes only stable releases that have been community-tested. 
+
+Prime also offers options for production support, as well as add-ons to your subscription that tailor to your commercial needs.
+
+To learn more and get started with Rancher Prime, please visit [this page](https://www.rancher.com/quick-start). 
+
+<CardSection
+    id="Gettingstarted"
+    icon={<RocketRegular />}
+>
+    <Card
+        title="Virtualization on Kubernetes with Harvester"
+        to="/integrations-in-rancher/harvester"
+    />
+    <Card
+        title="Cloud Native Storage with Longhorn"
+        to="/integrations-in-rancher/longhorn"
+    />
+    <Card
+        title="Container Security with NeuVector"
+        to="/integrations-in-rancher/neuvector"
+    />
+    <Card
+        title="Advanced Policy Management with Kubewarden"
+        to="/integrations-in-rancher/kubewarden"
+    />
+    <Card
+        title="Operating System Management with Elemental"
+        to="/integrations-in-rancher/elemental"
+    />
+    <Card
+        title="Observability with Opni"
+        to="/integrations-in-rancher/opni"
+    />
+    <Card
+        title="Continuous Delivery with Fleet"
+        to="/integrations-in-rancher/fleet"
+    />
+    <Card
+        title="Kubernetes on the Desktop"
+        to="/integrations-in-rancher/rancher-desktop"
+    />
+    <Card
+        title="Application Development Engine with Epinio"
+        to="/integrations-in-rancher/epinio"
+    />
+</CardSection>
@@ -48,4 +48,4 @@ Rancher supports several major cloud providers, but by default, these node drive

 There are several other node drivers that are disabled by default, but are packaged in Rancher:

-*   [Harvester](../integrations-in-rancher/harvester.md#harvester-node-driver/), available in Rancher v2.6.1
+*   [Harvester](../integrations-in-rancher/harvester/overview.md#harvester-node-driver/), available as of Rancher v2.6.1
@@ -149,7 +149,7 @@ To see options on how to customize the cert-manager install (including for cases

 ```
 # If you have installed the CRDs manually instead of with the `--set installCRDs=true` option added to your Helm install command, you should upgrade your CRD resources before upgrading the Helm chart:
-kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.11.0/cert-manager.crds.yaml
+kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/<VERSION>/cert-manager.crds.yaml

 # Add the Jetstack Helm repository
 helm repo add jetstack https://charts.jetstack.io
@@ -160,8 +160,7 @@ helm repo update
 # Install the cert-manager Helm chart
 helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager \
-  --create-namespace \
-  --version v1.11.0
+  --create-namespace
 ```

 Once you’ve installed cert-manager, you can verify it is deployed correctly by checking the cert-manager namespace for running pods: