Three ways into a cluster. One of them fits yours.
An environment connects a project to one cluster, with its own access level. Choose how SKYLINE reaches it by how the cluster can be reached.
Central kubeconfig
When the cluster API is reachable from SKYLINE. The kubeconfig is stored encrypted and never shown again.
In-cluster agent
When the cluster can connect out but nothing may connect in. No credentials on the SKYLINE server; commands run as the agent’s service account.
Engineer bridge
When the cluster is reachable only over your VPN. A small program on an engineer’s machine runs the commands with that engineer’s kubeconfig context.
A connection test
It checks that the cluster is reached, reads its version and verifies that the permissions match the access level.
Add an environment
- 01
Choose the access method
By how the cluster can be reached: directly, outbound only, or over a VPN.
- 02
Choose the access level
Read-only, write or full. Start with read-only; the level is a command allow-list the runner enforces.
- 03
Add context notes
Facts that help every investigation, such as where Prometheus runs or what is not installed.