zuul
/
zuul
Code Issues Proposed changes

docs: Clarify zuul_console behaviour for Kubernetes job nodes 

This change is related to Id3669418189f1083a2fb690ada0b60043a77b1d6
and clarifies the zuul_console connectivity behaviour when dealing
with Kubernetes-based job nodes.

Change-Id: I7191631dc54071d158657816a8cc10335e122df5
This commit is contained in:
Michael Kelly 2022-11-21 20:52:26 -08:00
parent 5d6a6fb1ad
commit 2c20d7a61d
No known key found for this signature in database
GPG Key ID: 77F7FE93040ECF3E
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/operation.rst
View File

@ -186,6 +186,13 @@ inventory). Live streaming of ``shell`` and ``command`` calls will of
course be unavailable in this case, but no spool files will be course be unavailable in this case, but no spool files will be
created. created.
For Kubernetes-based job nodes the connection from the executor to the
``zuul_console`` daemon is established by using ``kubectl port-forward``
to forward a local port to the appropriate port on the pod containing
the job node. If the Kubernetes user is not bound to a role that has
authorization for port-forwarding, this will prevent connection to
the ``zuul_console`` daemon.
Web Server Web Server
---------- ----------