From cbe1382880714c539ec2d646442865e786df415b Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Wed, 30 Mar 2022 10:30:43 +0530 Subject: [PATCH 1/2] Make amendments to the installation netowrking requirements --- content/rancher/v2.6/en/installation/requirements/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/rancher/v2.6/en/installation/requirements/_index.md b/content/rancher/v2.6/en/installation/requirements/_index.md index 3c089d6023c..d7a9168baf5 100644 --- a/content/rancher/v2.6/en/installation/requirements/_index.md +++ b/content/rancher/v2.6/en/installation/requirements/_index.md @@ -170,6 +170,8 @@ Rancher performance depends on etcd in the cluster performance. To ensure optima This section describes the networking requirements for the node(s) where the Rancher server is installed. +> If a server containing Rancher has the `X-Frame-Options=DENY` header, the Ember UI will be completely unreachable on upgrading from the legacy UI. This is because any screen written for the legacy UI is rendered as an embedded iframe within the new Dashboard. + ### Node IP Addresses Each node used should have a static IP configured, regardless of whether you are installing Rancher on a single node or on an HA cluster. In case of DHCP, each node should have a DHCP reservation to make sure the node gets the same IP allocated. From aca17a5e9751e0f0e496d830c3c59f4065f87bcf Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Tue, 5 Apr 2022 15:01:40 +0530 Subject: [PATCH 2/2] Amending per suggestions --- content/rancher/v2.6/en/installation/requirements/_index.md | 2 +- .../workload/quickstart-deploy-workload-ingress/_index.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/installation/requirements/_index.md b/content/rancher/v2.6/en/installation/requirements/_index.md index d7a9168baf5..c60d529b881 100644 --- a/content/rancher/v2.6/en/installation/requirements/_index.md +++ b/content/rancher/v2.6/en/installation/requirements/_index.md @@ -170,7 +170,7 @@ Rancher performance depends on etcd in the cluster performance. To ensure optima This section describes the networking requirements for the node(s) where the Rancher server is installed. -> If a server containing Rancher has the `X-Frame-Options=DENY` header, the Ember UI will be completely unreachable on upgrading from the legacy UI. This is because any screen written for the legacy UI is rendered as an embedded iframe within the new Dashboard. +> If a server containing Rancher has the `X-Frame-Options=DENY` header, some pages in the new Rancher UI will not be able to render after upgrading from the legacy UI. This is because some legacy pages are embedded as iFrames in the new UI. ### Node IP Addresses diff --git a/content/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/_index.md b/content/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/_index.md index 5be4b866fb9..004950b7fe2 100644 --- a/content/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/_index.md +++ b/content/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/_index.md @@ -54,6 +54,7 @@ Now that the application is up and running, it needs to be exposed so that other **Result:** The application is assigned a `sslip.io` address and exposed. It may take a minute or two to populate. + ### View Your Application From the **Deployments** page, find the **Endpoints** column for your deployment and click on an endpoint. The endpoints available will depend on how you configured the port you added to your deployment. For endpoints where you do not see a randomly assigned port, append the path you specified when creating the ingress to the IP address. For example, if your endpoint looks like `xxx.xxx.xxx.xxx` or `https://xxx.xxx.xxx.xxx` change it to `xxx.xxx.xxx.xxx/hello` or `https://xxx.xxx.xxx.xxx/hello`.