From a7d3c921cd9b967093009b46ca12f73e2863066f Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Tue, 7 Jun 2022 09:49:16 +0200 Subject: [PATCH] Update content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md Co-authored-by: Jen Travinski --- .../v2.6/en/installation/install-rancher-on-k8s/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md b/content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md index 1214b1e199c..dfe8619b5b7 100644 --- a/content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md +++ b/content/rancher/v2.6/en/installation/install-rancher-on-k8s/_index.md @@ -34,7 +34,7 @@ For help setting up a Kubernetes cluster, we provide these tutorials: The Rancher UI and API is exposed through an Ingress. This means the Kubernetes cluster, that you install Rancher in, must contain an Ingress controller -For RKE, RKE2 and K3s installations, you don't have to install the Ingress controller manually because one is installed by default. +For RKE, RKE2, and K3s installations, you don't have to install the Ingress controller manually because one is installed by default. For distributions that do not include an Ingress Controller by default, like a hosted Kubernetes cluster such as EKS, GKE, or AKS, you have to deploy an Ingress controller first. Note that the Rancher Helm chart does not set an `ingressClassName` on the ingress by default. Because of this, you have to configure the Ingress controller to also watch ingresses without an `ingressClassName`.