Kubeconfig Management
Geeper lets you create multiple kubeconfigs per cluster, each with its own permissions and scope. This makes it easy to give teammates or CI systems exactly the access they need — nothing more.
Creating a kubeconfig
Section titled “Creating a kubeconfig”- Open your cluster and go to the Access tab
- Click New kubeconfig
- Fill in the details:
- Name — a label so you can identify it later (e.g.
ci-readonly,alice-staging) - Role — the level of access (see below)
- Namespace — optionally restrict access to one or more namespaces (comma-separated). Leave blank for cluster-wide access.
- Expires — optionally set an expiry date. After this date the kubeconfig stops working.
- Name — a label so you can identify it later (e.g.
- Click Create — you’ll see the kubeconfig YAML once. Copy or download it now.
| Role | What it can do |
|---|---|
view | Read-only access to most resources |
edit | Create and update resources, no RBAC changes |
admin | Full access including RBAC within the cluster |
These map to the standard Kubernetes view, edit, and cluster-admin cluster roles.
Downloading again
Section titled “Downloading again”You can re-download a kubeconfig at any time from the Access tab — a fresh token is generated each time with the same expiry.
Revoking access
Section titled “Revoking access”Click the menu next to any kubeconfig and select Revoke. The credentials are invalidated immediately — there’s no waiting for a token to expire.