kubernetes_provider

Kubernetes implementation of the provider interface.

The server runs as a pod and starts every session as a pod in its own namespace, through its service account and the REST API, so a namespaced Role is all it needs and no namespace name is written anywhere. Storage reaches a session the way the server sees it: each server path is mounted from the volume that backs it, with a subPath; a volume only one node can mount (a ReadWriteOnce claim, a hostPath) pins sessions to the server's node. A session pod starts from the PodTemplate <owner>-session when the namespace has one, which is where node placement, runtime classes, and default resources belong; an application's template may name another PodTemplate, laid over it for that application's sessions. Session pods are labelled with the server's owner (its Deployment or StatefulSet) and owned by it, so uninstalling removes them too. Images are pulled by the kubelet, so pull_image pins the registry's current digest and sessions run that exact image.