public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-16 01:53:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

removing and updating registration url docs

Browse Source
This commit is contained in:
Mark Bishop
2018-12-20 17:08:54 -07:00
committed by Denise
parent f27eca4ab2
commit 61f55885d8
3 changed files with 13 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/admin-settings/_index.md
+1 -7
View File
@@ -6,10 +6,4 @@ aliases:
- /rancher/v2.x/en/tasks/global-configuration/
---
After installing Rancher 2.x, you should
1. Set a Rancher Server URL, which your cluster nodes will use to resolve with Rancher. You'll be prompted to set this URL upon your first log in.
2. Set up external user authentication and permissions so that your organization can log into Rancher.
After making these initial configurations, you might also want to configure one or more _pod security policies_, which are sets of conditions that your pods must meet for Kubernetes to allow them to run.
After installation, the system administrator should configure Rancher to configure security, default settings, and user access.
content/rancher/v2.x/en/admin-settings/log-in/_index.md
+12
View File
@@ -0,0 +1,12 @@
---
title: First Log In
weight: 50
aliases:
- /rancher/v2.x/en/concepts/global-configuration/server-url/
- /rancher/v2.x/en/tasks/global-configuration/server-url/
- /rancher/v2.x/en/admin-settings/server-url
---
After you log into Rancher for the first time, Rancher will prompt you for a **Rancher Server URL**.You should set the URL to the main entry point to the Rancher Server. When a load balancer sits in front a Rancher Server cluster, the URL should resolve to the load balancer. The system will automatically try to infer the Rancher Server URL from the IP address or host name of the host running the Rancher Server. This is only correct if you are running a single node Rancher Server installation. In most cases, therefore, you need to set the Rancher Server URL to the correct value yourself.
>**Important!** After you set the Rancher Server URL, we do not support updating it. Set the URL with extreme care.
content/rancher/v2.x/en/admin-settings/server-url/_index.md
-18
View File
@@ -1,18 +0,0 @@
---
title: Rancher Server URL
weight: 1105
aliases:
- /rancher/v2.x/en/concepts/global-configuration/server-url/
- /rancher/v2.x/en/tasks/global-configuration/server-url/
---
This is the URL of your Rancher Server. All nodes in your cluster must resolve to this URL. This is also the URL that serves the Rancher API.
You are prompted for this URL upon the very first Rancher login. You should set the URL to the main entry point to the Rancher Server. When a load balancer fronts a Rancher Server cluster, the URL should resolve to the load balancer. The system will automatically try to infer the Rancher Server URL from the IP address or host name of the host running the Rancher Server. This is only correct if you are running a single node Rancher Server installation. In most cases, therefore, you need to set the Rancher Server URL to the correct value yourself.
Even though you can edit the Rancher Server URL later in the **Settings** UI from the **Global** view, updating the Rancher Server URL must be done with extreme care.
- You must also update the SSL certificates to match the new URL.
- Unless you make sure the old URL continues to work, you will have to re-register all the nodes and clusters so that they point to the new Rancher Server URL.