public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 21:18:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Ingress nginx replacement (#2237)

Browse Source 
* Replace/remove ingress-nginx references

* Add links to annotations + remove example using unsupported annotation
This commit is contained in:
Billy Tat
2026-03-19 11:14:14 -07:00
committed by GitHub
parent 8fbc785b2c
commit b6192dee43
76 changed files with 94 additions and 662 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md
+1 -1
View File
@@ -69,7 +69,7 @@ Specifically, the value should be a comma-delimited string which only contains I
- Your cluster is registered and assigned a state of **Pending**. Rancher is deploying resources to manage your cluster.
- You can access your cluster after its state is updated to **Active**.
- **Active** clusters are assigned two Projects: `Default` (containing the namespace `default`) and `System` (containing the namespaces `cattle-system`, `ingress-nginx`, `kube-public` and `kube-system`, if present).
- **Active** clusters are assigned two Projects: `Default` (containing the namespace `default`) and `System` (containing the namespaces `cattle-system`, `traefik`, `kube-public` and `kube-system`, if present).
:::note
versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/eks.md
+1 -1
View File
@@ -63,7 +63,7 @@ You can access your cluster after its state is updated to **Active**.
**Active** clusters are assigned two Projects:
- `Default`, containing the `default` namespace
- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
- `System`, containing the `cattle-system`, `traefik`, `kube-public`, and `kube-system` namespaces
## EKS Cluster Configuration Reference
versioned_docs/version-2.12/how-to-guides/new-user-guides/kubernetes-clusters-in-rancher-setup/set-up-clusters-from-hosted-kubernetes-providers/gke.md
+1 -1
View File
@@ -75,7 +75,7 @@ You can access your cluster after its state is updated to **Active**.
**Active** clusters are assigned two Projects:
- `Default`, containing the `default` namespace
- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
- `System`, containing the `cattle-system`, `traefik`, `kube-public`, and `kube-system` namespaces
## Private Clusters
versioned_docs/version-2.12/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/create-a-digitalocean-cluster.md
+1 -1
View File
@@ -48,7 +48,7 @@ You can access your cluster after its state is updated to **Active**.
**Active** clusters are assigned two Projects:
- `Default`, containing the `default` namespace
- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
- `System`, containing the `cattle-system`, `traefik`, `kube-public`, and `kube-system` namespaces
## Optional Next Steps
versioned_docs/version-2.12/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/create-a-google-compute-engine-cluster.md
+1 -1
View File
@@ -78,7 +78,7 @@ You can access your cluster after its state is updated to **Active**.
**Active** clusters are assigned two Projects:
- `Default`, containing the `default` namespace
- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
- `System`, containing the `cattle-system`, `traefik`, `kube-public`, and `kube-system` namespaces
### GCE Best Practices
versioned_docs/version-2.12/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/create-an-amazon-ec2-cluster.md
+1 -1
View File
@@ -64,7 +64,7 @@ You can access your cluster after its state is updated to **Active**.
**Active** clusters are assigned two Projects:
- `Default`, containing the `default` namespace
- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
- `System`, containing the `cattle-system`, `traefik`, `kube-public`, and `kube-system` namespaces
### Optional Next Steps
versioned_docs/version-2.12/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/create-an-azure-cluster.md
+1 -1
View File
@@ -87,7 +87,7 @@ You can access your cluster after its state is updated to **Active**.
**Active** clusters are assigned two Projects:
- `Default`, containing the `default` namespace
- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
- `System`, containing the `cattle-system`, `traefik`, `kube-public`, and `kube-system` namespaces
### Optional Next Steps
versioned_docs/version-2.12/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/nutanix/provision-kubernetes-clusters-in-aos.md
+1 -1
View File
@@ -85,7 +85,7 @@ You can access your cluster after its state is updated to **Active**.
**Active** clusters are assigned two Projects:
- `Default`, containing the `default` namespace
- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
- `System`, containing the `cattle-system`, `traefik`, `kube-public`, and `kube-system` namespaces
## Optional Next Steps
versioned_docs/version-2.12/how-to-guides/new-user-guides/launch-kubernetes-with-rancher/use-new-nodes-in-an-infra-provider/vsphere/provision-kubernetes-clusters-in-vsphere.md
+1 -1
View File
@@ -86,7 +86,7 @@ You can access your cluster after its state is updated to **Active**.
**Active** clusters are assigned two Projects:
- `Default`, containing the `default` namespace
- `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
- `System`, containing the `cattle-system`, `traefik`, `kube-public`, and `kube-system` namespaces
## Optional Next Steps