nodepool/doc/source/openshift-pods.rst

zuul

Openshift Pods Driver

Selecting the openshift pods driver adds the following options to the providers section of the configuration.

providers.[openshiftpods]

The Openshift Pods driver is similar to the Openshift driver, but it only supports pod label. This enables using an unprivileged service account that doesn't require the self-provisioner role.

Example:

providers:
  - name: cluster
    driver: openshiftpods
    context: unprivileged-context-name
    pools:
      - name: main
        labels:
          - name: openshift-pod
            image: docker.io/fedora:28

context

Name of the context configured in kube/config.

Before using the driver, Nodepool services need a kube/config file manually installed. Make sure the context is present in oc config get-contexts command output.

launch-retries

The number of times to retry launching a pod before considering the job failed.

max-pods

Maximum number of pods that can be used.

pools

A pool defines a group of resources from an Openshift provider.

name

The project's (namespace) name that will be used to create the pods.

priority

The priority of this provider pool (a lesser number is a higher priority). Nodepool launchers will yield requests to other provider pools with a higher priority as long as they are not paused. This means that in general, higher priority pools will reach quota first before lower priority pools begin to be used.

This setting may be specified at the provider level in order to apply to all pools within that provider, or it can be overridden here for a specific pool.

node-attributes

A dictionary of key-value pairs that will be stored with the node data in ZooKeeper. The keys and values can be any arbitrary string.

labels

Each entry in a pool`s labels section indicates that the corresponding label is available for use in this pool.

Each entry is a dictionary with the following keys

name

Identifier for this label; references an entry in the labels section.

image

The image name.

image-pull

The ImagePullPolicy, can be IfNotPresent, Always or Never.

image-pull-secrets

The imagePullSecrets needed to pull container images from a private registry.

Example:

labels:
  - name: openshift-pod
    type: pod
    image: docker.io/fedora:28
    image-pull-secrets:
      - name: registry-secret

cpu

The number of cpu to request for the pod.

memory

The amount of memory in MB to request for the pod.

python-path

The path of the default python interpreter. Used by Zuul to set ansible_python_interpreter. The special value auto will direct Zuul to use inbuilt Ansible logic to select the interpreter on Ansible >=2.8, and default to /usr/bin/python2 for earlier versions.

shell-type

The shell type of the node's default shell executable. Used by Zuul to set ansible_shell_type. This setting should only be used

• For a windows pod with the experimental connection-type ssh, in which case cmd or powershell should be set and reflect the node's DefaultShell configuration.
• If the default shell is not Bourne compatible (sh), but instead e.g. csh or fish, and the user is aware that there is a long-standing issue with ansible_shell_type in combination with become

env

A list of environment variables to pass to the Pod.

name

The name of the environment variable passed to the Pod.

value

The value of the environment variable passed to the Pod.

node-selector

A map of key-value pairs to ensure the OpenShift scheduler places the Pod on a node with specific node labels.