openstack-ironic/ironic/console
Steve Baker 28168c4168 Add a kubernetes provider for console container
A new ``ironic.console.container`` provider is added called
``kubernetes`` which allows Ironic conductor to manage console
containers as Kubernetes pods. The kubernetes resources are defined in
the template file configured by ``[vnc]kubernetes_container_template``
and the default template creates one secret to store the app info, and
one pod to run the console container.

It is expected that Ironic conductor is deployed inside the kubernetes
cluster. The associated service account will need roles and bindings
which allow it to manage the required resources (with the default
template this will be secrets and pods).

This provider holds the assumption that ironic-novnc will be deployed in
the same kubernetes cluster, and so can connect to the VNC servers via
the pod's ``status.hostIP``.

Assisted-By: gemini
Change-Id: Ib91f7d7c15be51d68ebf886e44efaf191a14437b
Signed-off-by: Steve Baker <sbaker@redhat.com>
2025-12-04 11:25:05 -08:00
..
container Add a kubernetes provider for console container 2025-12-04 11:25:05 -08:00
rfb Add ironic-novncproxy service 2025-02-19 20:17:57 +00:00
securityproxy Add ironic-novncproxy service 2025-02-19 20:17:57 +00:00
__init__.py Add ironic-novncproxy service 2025-02-19 20:17:57 +00:00
novncproxy_service.py vncproxy: Use dedicated options for SSL 2025-03-08 05:20:59 +09:00
websocketproxy.py Clean-up misc eventlet references 2025-08-18 16:54:00 +00:00