public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-10 03:05:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

moved new flag, revised : to =, updated/reworded mention of new in 2.6 in same section

Browse Source
This commit is contained in:
martyav
2023-06-13 18:25:52 -04:00
parent 5e09d888a8
commit 0c37084d19
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-gke.md
+7 -4
View File
@@ -153,7 +153,6 @@ helm upgrade --install \
ingress-nginx ingress-nginx/ingress-nginx \
--namespace ingress-nginx \
--set controller.service.type=LoadBalancer \
--set service.type: NodePort \
--version 4.0.18 \
--create-namespace
```
@@ -189,12 +188,16 @@ Next, install the Rancher Helm chart by following the instructions on [this page
Use the DNS name from the previous step as the Rancher server URL when you install Rancher. It can be passed in as a Helm option. For example, if the DNS name is `rancher.my.org`, you could run the Helm installation command with the option `--set hostname=rancher.my.org`.
**_New in v2.6.7_**
When installing Rancher on top of this setup, you will also need to pass the value below into the Rancher Helm install command in order to set the name of the ingress controller to be used with Rancher's ingress resource:
When installing Rancher on top of this setup, you will also need to set the name of the ingress controller to be used with Rancher's ingress resource:
```
--set ingress.ingressClassName=nginx
```
Refer [here for the Helm install command](../../../pages-for-subheaders/install-upgrade-on-a-kubernetes-cluster.md#5-install-rancher-with-helm-and-your-chosen-certificate-option) for your chosen certificate option.
In Rancher v2.7.5, if you intend to use the default GKE ingress on your cluster, you need to set the following flag:
```
--set service.type=NodePort
```