zuul-jobs/roles/use-buildset-registry
James E. Blair b6cb191295 Add cri-o support to use-buildset registry
This lets use-buildset-registry notify cri-o about the new
registries.conf file if it is being used as the container backend
for k8s.

Change-Id: Ia1805519ab4b6bb5f79df0492f702effc6a3e024
2020-01-07 07:35:28 -08:00
..
defaults use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00
library use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00
module_utils use-buildset-registry: Vendor pytoml and remarshal 2019-12-03 14:10:23 -08:00
tasks Add cri-o support to use-buildset registry 2020-01-07 07:35:28 -08:00
vars openshift speculative containers 2019-12-06 13:50:25 -08:00
__init__.py use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00
README.rst use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00

Adds a buildset registry to the docker configuration.

Use this role on any host which should use the buildset registry.

Role Variables

Information about the registry, as returned by :zuulrun-buildset-registry.

The host (IP address) of the registry.

The port on which the registry is listening.

The username used to access the registry via HTTP basic auth.

The password used to access the registry via HTTP basic auth.

The (self-signed) certificate used by the registry.