zuul/nodepool
Code Issues Proposed changes

Update documentation for k8s in-cluster config

Browse Source 
Update the docs and add a release note to let folks know that
in-cluster config is an option now.

Change-Id: Ifb4a575fb7e9b6a89e14f00a2e1cccee6fdabf72
This commit is contained in:
James E. Blair 2019-07-02 06:50:19 -07:00
parent e819f4b4b1
commit 676b6b07bd
2 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/configuration.rst
View File

@ -1164,13 +1164,15 @@ Selecting the kubernetes driver adds the following options to the
.. attr:: context
:required:
Name of the context configured in ``kube/config``.
Before using the driver, Nodepool services need a
``kube/config`` file manually installed with cluster admin
context.
Before using the driver, Nodepool either needs a ``kube/config``
file installed with a cluster admin context, in which case this
setting is required, or if Nodepool is running inside
Kubernetes, this setting and the ``kube/config`` file may be
omitted and Nodepool will use a service account loaded from the
in-cluster configuration path.
.. attr:: launch-retries
:default: 3

8
releasenotes/notes/k8s-in-cluster-config-e9a711d20faac949.yaml Normal file
View File

@ -0,0 +1,8 @@
---
features:
- |
The Kubernetes driver now supports optionally loading cluster
admin service account information from the standard in-cluster
configuration paths if Nodepool itself is running in Kubernetes.
If this method is used, installation of a ``kube/config`` file in
the Nodepool launcher pod is no longer required.