Next steps¶

You've now seen kubelatch working on your machine. Here's what to read next depending on what you're going to do with it.

You're going to use kubelatch with your team¶

Your team already has kubelatch deployed and you want to work with it day to day.

1. Sign in and request access: the invitation, the login, and what to ask an administrator for.
2. The CLI, or get a credential from the web, and use it with kubectl, k9s, Lens and Helm.
3. Expiry and revocation and My activity.
4. If your pipelines deploy to Kubernetes: Credentials for GitHub Actions.

You're going to install and operate it¶

You want to bring it to a real environment for your organization.

1. Install on a management cluster, with TLS and Postgres.
2. OIDC login (SSO) or GitHub login, so people sign in with their company or organization account.
3. Register a cluster and Grant permissions: what you did in the tutorial, for real. When the system roles don't fit, Manage roles.
4. Users and bots, CI: trust rules and Audit and retention.
5. Before production: Accounts and recovery and Upgrades and backups.

You want to understand why¶

You want to know what happened under the hood at each step of the tutorial.

• Architecture: the three pieces and where state lives.
• The journey of a request: what kubelatch does with your kubectl get pods.
• System roles: why debugger required the Pod Security Admission label, and Roles, for composing your own.
• Security model and Why a proxy.

The exact details (environment variables, API routes, errors) are in the Reference.