zuul-jobs/roles/use-buildset-registry
Jan Gutter 83bfd5b917
Update ensure-kubernetes with podman support
* This adds some extra options to the ensure-kubernetes role:
  * podman + cri-o can now be used for testing
  * This mode seems to be slightly more supported than the
    current profiles.
* The location for minikube install can be moved.
* The use-buildset-registry role needed slight updates in order
  to populate the kubernetes registry config early.

Change-Id: Ia578f1e00432eec5d81304f70db649e420786a02
2024-08-22 20:50:39 +01:00
..
defaults Update ensure-kubernetes with podman support 2024-08-22 20:50:39 +01:00
library use-buildset-registry: add URL to buildset_registry_namespaces 2023-01-08 08:05:33 -08:00
module_utils use-buildset-registry: remove useless import 2021-10-28 12:48:06 -04:00
tasks Update ensure-kubernetes with podman support 2024-08-22 20:50:39 +01:00
vars use-buildset-registry: add Fedora certifacts vars 2020-04-30 17:34:04 +00:00
__init__.py use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00
README.rst Update ensure-kubernetes with podman support 2024-08-22 20:50:39 +01: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.