[khuyentran1401]

Why

The quickstart sends new users to the Keycloak admin console to create an account, using kubectl and jq to get the admin password. Since v0.15.0, nic creates an admin account and nic outputs prints the passwords, so users can sign in right after deploying.

Reference Issues or PRs

Part of #764.

What does this implement/fix?

• The quickstart now has users sign in as admin with the password from nic outputs, instead of creating a user in Keycloak first.
• The Keycloak authentication guide gets the admin console password from nic outputs instead of kubectl and jq, and no longer says nic doesn't create an account.

Testing

• Did you test the pull request locally?

• Did you add new tests?

• Deployed locally with nic v0.15.0 and signed in as admin with the nic outputs password, which reaches the landing page.

• Checked the nic source: the admin account and the nic outputs labels are the same in v0.16.0.

[github-actions]

Docs preview for docs/quickstart-fixes-nic-v0-15:

• Nebari (via the nebari-docs Worker): https://docs-quickstart-fixes-nic-v0-15-nebari-docs.openteams-account.workers.dev
• Nebari Classic (via the nebari-docs-classic Worker): https://docs-quickstart-fixes-nic-v0-15-nebari-docs-classic.openteams-account.workers.dev

[jbouder]

Really nice update. Didn't know about this :)