SSH Keys
SSH keys are public keys you register so node pools can trust them for the host access patterns your organization uses. They are not a replacement for Kubernetes RBAC or kubeconfig.
Keys created here can be used for access to your clusters where the platform expects them. Only ever paste public keys into the portal.
What you see in the panel
The page lists keys with name, fingerprint, and created and updated times. Use Add SSH key, search by name or public key, clear sorting, and refresh. Row menus manage individual keys.
When to use it
Register keys when you need SSH-based access to nodes for diagnostics your team allows, or when new node pools should inherit a known set of operator keys.
Tutorial: add and manage keys
Open SSH Keys
From Products in the sidebar, open SSH Keys.
Add a public key
Click Add SSH key. Give a clear label per person or automation identity, paste only the public key material, and save.
Use the key with node pools
When creating or updating node pools that require it, select the registered key. See Clusters.
Rotate and remove
Remove keys that no longer belong to active operators. Prefer one key per person or automation identity.
Never paste private keys:
Do not upload private keys, put them in tickets, or share them in chat. If a private key may be exposed, generate a new key pair and remove the old public key from the portal.