Clusters

Before Planeo can deploy applications it needs to know where to deploy them to. Rather than having Planeo pick a context, we prefer an opt-in approach where users specifically map Planeo Clusters to specific Kubernetes contexts they want to use. This helps contextualize different access paths to different K8s endpoints, around different purposes.

Planeo will load discoverable clusters from your standard configuration files, and present them as options. Non standard locations are not currently supported. Pick a name for a context, and select a kubeconfig file from the dropdown, and then select a path.

After clicking Add your cluster should get verified and added. Unless there are issues, it should enter a green "ready" status, and be available for use.

If your cluster becomes unreachable, either because a local test cluster has stopped or perhaps auth has expired, the status will become errored in Planeo. A cluster being in a non-ready state prevents updates to dependent environments and stacks from taking place until the cluster is reachable again. This is often reflected as stacks going into a pre-ready state or an error state.

As soon as the cluster becomes available again you can refresh the cluster via the UI, and it should cascade to all associated environments and stacks, so if you fix the issue, ensuring kubectl works with the referenced context, just click on the refresh icon in the actions column.