Skip to Content
ReferenceAfter signing in to corectl

Continue with corectl

Your browser sign-in has returned to corectl. Check your terminal for the final login result and selected context before running commands. corectl still needs to confirm API access and save your credentials; this help page cannot check your local login status.

Once the terminal confirms login, you’re ready to explore your context. For example:

Logged in to core-platform/engineering-test (Engineering Test) as user@example.com

core-platform/engineering-test is the context key used in commands; Engineering Test is the context display label. An additional Current context: ... line appears only when your saved default differs from the context you just signed in to, such as when using auth login --context with another saved context. That line identifies the default used by subsequent commands without an explicit --context.

Try your first commands

Check the exact context, context display name and account you’re using:

corectl auth whoami

List the clusters available to your context:

corectl get clusters

List your saved contexts:

corectl config get-contexts

For available commands and flags:

corectl --help

Choose where to work

Most users can keep the context selected during login. If you need to switch, use an exact context name from corectl config get-contexts:

corectl config use-context core-platform/engineering-test

The context above is an example; use one listed in your terminal.

See the corectl guide for context selection, additional instances, JSON and YAML output, and logout. You can also install and manage cluster agents and configure kubectl for a registered cluster using existing local credentials. Application creation is not currently supported.

For additional diagnostic details, use the global -v / --verbose flag. Diagnostics go to stderr and leave command results, including JSON and YAML, on stdout. See diagnostic output for examples.

If the terminal reports an error

Follow the terminal’s message before retrying. Login needs access to your instance and an unlocked macOS Keychain or Linux Secret Service to save credentials. Opening this page alone does not sign you in.

You can close this tab whenever you’re ready to return to your terminal.