In the Admin -> Settings page of Rancher, we allow customization of Rancher for different areas of the product.
Before launching any hosts, you will be asked to complete the host registration. This registration sets up how your Rancher server is going to connect with your hosts. If you have already set up access control, you will not be prompted to set host registration as Rancher assumes that your URL will be accessible.
The setup determines the base URL your hosts will use to connect to the Rancher API. By default, Rancher selects the base URL you used to access the UI. If you choose to change the address, make sure to specify the port that should be used to connect to the Rancher API. If you are configuring Rancher with SSL, be sure to change the protocol to
https. This registration setup determines what the command will be for adding custom hosts.
If access control is turned on for Rancher, only the admin will be able to change the host registration. By default, the first admin is the first user to authenticate with Rancher when access control was configured. If access-control is still not configured, any users to the site can update the host registration. This option can be updated in the Admin -> Host Registration tab.
By default, the catalog is enabled with three catalogs:
As the settings page is only available for admins, only admins have the ability to add private catalogs to Rancher. Adding a catalog is as simple as adding a catalog name and the git URL. The correct format of the git URL can be found here. Whenever you add a catalog, it will be immediately available in the catalog.
If you want to create your own private catalog to add, the git repository must be set up in a specific format.
By default, Rancher asks you to opt in to collect anonymous statistics about the configuration of Rancher. This data allows us to better understand our user base and how to make Rancher better. Read more about telemetry in Rancher.