* gerundify Configuration for Storage Classes in Azure * gerundify Authentication Config * gerundify Bootstrap Password * gerundify and disambiguate manage-PSP * gerundify and disambiguate create-PSP * syncing? Syncing what? * updating label for Configure OpenLDAP * updating label for authentication config * updating label for configuring microsoft ad and shibboleth (saml) * updating label for configuring microsoft ad and shibboleth (saml) in sidebars (last commit covered versioned docs) * label + title for one of several sets of pages entitled role-based access control * gerundify Upgrade a Hardened Custom/Imported Cluster to Kubernetes v1.25 * re-order title of Certificate Troubleshooting so verb comes first * added 'about' to title because the page is about drivers that provision, not how to provision a driver * template enforcement > enforcing templates * update label to match title - deploy > deploying * updated label to matach title - manage clusters > cluster administration * gerundify set up in infrastructure setup section * typo fix - spacing * matching label to title - launch > launching * label matching title - set up part 2 * label matching title - windows clusters * how to configure > configuring * using > launching (partially matches label to title) * ingress config > configging an ingress * match label to title - project administration * match label to title - project resource quotas * match title to label - monitoring/alerting guides * matching label to title - enabling * gerundify allow unsupported storage drivers * Update openapi/swagger.json * lost metadata syntax re-applied * Apply suggestions from code review
1.7 KiB
title
| title |
|---|
| Setting up the Bootstrap Password |
When Rancher starts for the first time, a password is randomly generated for the first admin user. When the admin first logs in to Rancher, the UI shows commands that can be used to retrieve the bootstrap password. The admin needs to run those commands and log in with the bootstrap password. Then Rancher gives the admin an opportunity to reset the password.
The bootstrap password is randomly generated if it is not set during installation with a variable. For details on how to set the bootstrap password using a variable, see below.
Specifying the Bootstrap Password in Helm Installs
For a Helm install, users can specify the bootstrap password variable by configuring it in the Helm chart values with .Values.bootstrapPassword.
The password will be stored in a Kubernetes secret. After Rancher is installed, the UI will show instructions for how to retrieve the password using kubectl:
kubectl get secret --namespace cattle-system bootstrap-secret -o go-template='{{ .data.bootstrapPassword|base64decode}}{{ "\n" }}'
Specifying the Bootstrap Password in Docker Installs
For a Docker install, you can specify the bootstrap password by passing -e CATTLE_BOOTSTRAP_PASSWORD=password to the Docker install command.
The password will be stored in the Docker container logs. After Rancher is installed, the UI will show instructions for how to retrieve the password using the Docker container ID:
docker logs container-id 2>&1 | grep "Bootstrap Password:"