-
Notifications
You must be signed in to change notification settings - Fork 214
fix: password in console #4552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
fix: password in console #4552
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
1acd443
remove unsecure example of handling creating secrets with sensitive data
sosa-vaadin 8b89859
add suggested example
sosa-vaadin a22784b
Merge branch 'v24' into fix/password-in-console
heruan 468e101
Merge branch 'v24' into fix/password-in-console
peholmst File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -62,13 +62,16 @@ kubectl -n control-center edit configmap control-center | |
|
|
||
| === Secret for Control Center User Credentials | ||
|
|
||
| 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: | ||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
| [source,bash] | ||
| ---- | ||
| kubectl -n control-center create secret generic control-center-user \ | ||
| [email protected] \ | ||
| --from-literal=password=examplepassword123 | ||
| --from-file=password=/path/to/password.txt | ||
| ---- | ||
|
|
||
| You'll have to adjust these values, though, for your email address and password. | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.