Skip to content

Commit 02907e6

Browse files
committed
remove unsecure example of handling creating secrets with sensitive data
1 parent c66f37f commit 02907e6

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/control-center/getting-started/upgrade.adoc

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,13 +62,16 @@ kubectl -n control-center edit configmap control-center
6262

6363
=== Secret for Control Center User Credentials
6464

65-
You'll need to set up a secret which holds the email and password of the main Control Center user. These values must be the same as what was entered during the installation process of version 1.0, in the installation wizard. Assuming the email was `[email protected]` and the password was `examplepassword123`, you would execute the following:
65+
You'll need to set up a secret which holds the email and password of the main Control Center user.
66+
These values must be the same as what was entered during the installation process of version 1.0, in the installation wizard.
67+
68+
WARNING: To prevent the sensitive values of the secrets being *stored in the terminal command history*, write down the values in files (*without* an extra newline character at the end of the text) and pass those files to `kubectl` to save their content as the secret's values.
6669

6770
[source,bash]
6871
----
6972
kubectl -n control-center create secret generic control-center-user \
7073
71-
--from-literal=password=examplepassword123
74+
--from-file=password=/path/to/password.txt
7275
----
7376

7477
You'll have to adjust these values, though, for your email address and password.

0 commit comments

Comments
 (0)