all:
  children:
    controllers:
      hosts:
        controller: null
    zuul_unreachable:
      hosts: {}
  hosts:
    controller:
      ansible_connection: ssh
      ansible_host: 162.253.55.205
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      ci: true
      cilium_helm_values:
        operator:
          replicas: 1
      cilium_ipv4_cidr: 172.24.0.0/16
      kube_vip_address: 172.17.0.100
      kube_vip_interface: '{{ ansible_facts[''default_ipv4''].interface }}'
      kubernetes_coredns_node_selector:
        node-role.kubernetes.io/control-plane: ''
      kubernetes_hostname: '{{ ansible_facts[''default_ipv4''].address }}'
      kubernetes_version: 1.34.0
      molecule_install_collection_siblings: true
      molecule_scenario: download-binaries
      nodepool:
        az: yul2
        cloud: public
        external_id: 26fba432-33fc-4870-b630-d35524b126e3
        host_id: c3e8ca29246a1ecab67f48b7a3961d6a6b6d42e4a1646ddd3e849c9c
        interface_ip: 162.253.55.205
        label: debian-trixie
        node_properties: {}
        private_ipv4: 162.253.55.205
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.205
        public_ipv6: 2604:e100:1:0:f816:3eff:fe2d:572b
        region: ca-ymq-1
        slot: null
      zuul_node:
        az: yul2
        cloud: public
        external_id: 26fba432-33fc-4870-b630-d35524b126e3
        host_id: c3e8ca29246a1ecab67f48b7a3961d6a6b6d42e4a1646ddd3e849c9c
        interface_ip: 162.253.55.205
        label: debian-trixie
        node_properties: {}
        private_ipv4: 162.253.55.205
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.205
        public_ipv6: 2604:e100:1:0:f816:3eff:fe2d:572b
        region: ca-ymq-1
        slot: null
        uuid: null
  vars:
    ci: true
    cilium_helm_values:
      operator:
        replicas: 1
    kubernetes_coredns_node_selector:
      node-role.kubernetes.io/control-plane: ''
    kubernetes_version: 1.34.0
    molecule_install_collection_siblings: true
    molecule_scenario: download-binaries
    zuul:
      _inheritance_path:
      - '<Job base explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/zuul-config/zuul.d/jobs.yaml@main#1>'
      - '<Job molecule explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/zuul-jobs/zuul.d/ansible-jobs.yaml@main#1>'
      - '<Job ansible-collection-kubernetes-molecule explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/ansible-collection-kubernetes/.zuul.yaml@main#49>'
      - '<Job ansible-collection-kubernetes-molecule-download-binaries explicit: None
        implied: {MatchAny:{ImpliedBranchMatcher:main}} source: vexxhost/ansible-collection-kubernetes/.zuul.yaml@main#172>'
      - '<Job ansible-collection-kubernetes-molecule-download-binaries explicit: None
        implied: None source: vexxhost/ansible-collection-kubernetes/.zuul.yaml@main#224>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: 310bb293bb874f9daa2c6b6575fb4508
      build_refs:
      - branch: main
        change: '302'
        change_message: "fix(kubernetes): keep role arguments in the stored kubeadm
          configuration\n\nkubeadm only reads `/etc/kubernetes/kubeadm.yaml` for `kubeadm
          init`. `kubeadm join` and `kubeadm upgrade` render the control plane from
          the `ClusterConfiguration` stored in the `kube-system/kubeadm-config` ConfigMap,
          which the role never updates. So anything added to the role's component
          arguments after a cluster was created never reaches it:\n\n- **bind-address**
          ([Zendesk #370829](https://vexxhost.zendesk.com/agent/tickets/370829)):
          clusters created before #121 don't store `bind-address: 0.0.0.0` for kube-scheduler
          and kube-controller-manager. Every upgrade, and every control plane node
          that joins, puts them back on `127.0.0.1`, and their metrics and health
          endpoints stop answering on the node IPs. The customer saw this on a 1.28
          \u2192 1.29 upgrade, and we reproduced it with 3.4.0.\n- **`kubernetes_kubeadm_extra_args`
          (#322)**: overrides for `etcd`, `apiServer`, `controllerManager` and `scheduler`
          only land in the local file, so they never apply to existing clusters, even
          though the defaults say they apply on upgrades.\n\n**This PR**\n\n- Adds
          a `vexxhost.kubernetes.kubeadm_cluster_args` filter. It merges component
          arguments into a `ClusterConfiguration` in the format of the configuration's
          own API version: a mapping before `v1beta4`, a name/value list from it.\n
          \ - Arguments the role sets replace stored ones with the same name, including
          repeated `v1beta4` entries.\n  - Other stored arguments are kept, in order.\n
          \ - `null` removes an argument, the same as in #322, so an override can
          also clean up a stale stored argument such as an old `oidc-username-claim`.\n
          \ - External etcd is left alone.\n- `cluster-configuration.yml` runs right
          after `kubeadm init`, before any node joins and before `kubeadm upgrade
          apply`. On the bootstrap node it reads the ConfigMap with `kubernetes.core.k8s_info`,
          merges `kubernetes_kubeadm_{etcd,api_server,controller_manager,scheduler}_args`,
          and writes it back with `kubernetes.core.k8s` only when the parsed configuration
          changes. A cluster the role just created already matches, so it is left
          alone, and check mode reports the change without writing it.\n- `control-plane.yml`
          now installs the Python `kubernetes` package before bootstrapping, so those
          modules also work on a new cluster's first run. The two install blocks are
          moved, not changed.\n- kubeadm applies the stored arguments the next time
          it writes the components, during an upgrade or a control plane join. Running
          the role doesn't restart anything.\n- Documents this in the role README
          and the `kubernetes_kubeadm_extra_args` defaults comment.\n\n**Behaviour
          change for old clusters:** on their next upgrade, existing clusters get
          every argument a new cluster gets. Besides `bind-address`, clusters created
          before the role set `tls-min-version` (Kubernetes 1.28) will now require
          TLS 1.3 on etcd, the API server, the controller manager and the scheduler.
          Clients that can't do TLS 1.3 would need `tls-min-version: null` in `kubernetes_kubeadm_extra_args`
          for the affected component.\n\n**Validation**\n\n- Unit tests for the filter
          cover both formats, kept and replaced arguments, repeated `v1beta4` entries,
          `null` removal, missing sections, external etcd and idempotence. Role-level
          tests check that a cluster rendered by the role on 1.28, 1.30, 1.31 and
          1.34 comes out unchanged, that old clusters get `bind-address` back, and
          that `kubernetes_kubeadm_extra_args` overrides reach the stored copy. All
          114 unit tests pass, along with pre-commit (including ansible-lint).\n-
          Ran `cluster-configuration.yml` with `ansible-playbook` against a local
          kube-apiserver (envtest 1.34.1), with `kubernetes.core` 2.4.2 and 6.6.0,
          for a stored `v1beta4` config (1.33) and a `v1beta3` config (1.28), both
          missing `bind-address`. The first run added `bind-address: 0.0.0.0` and
          kept the other stored settings and the ConfigMap's other keys. The second
          run skipped the write. Check mode reported the change and left the ConfigMap
          untouched.\n- `kubeadm config validate` (1.34.0 and 1.29.15) accepts both
          merged configurations. `kubeadm init phase control-plane {scheduler,controller-manager}
          --dry-run` (1.34.0) renders `--bind-address=0.0.0.0` from the merged `v1beta4`
          config.\n- **CI:** the cluster-upgrade jobs (three controllers, 1.33.4 \u2192
          1.34.0 and 1.30.14 \u2192 1.31.14) now remove `bind-address` from the stored
          configuration after deploying the old version, which reproduces the customer's
          cluster. After the upgrade they check that `/healthz` on ports 10257 and
          10259 answers on every controller's IP.\n\nClusters that already went through
          an upgrade get the corrected configuration stored on the next run, but their
          manifests keep `127.0.0.1` until the next upgrade or a manual fix of the
          static pod manifests.\n\nCloses CLOUD-183.\n"
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/302
        commit_id: e1169c1f4dee2fdf281c23d31880991b5a70208b
        patchset: e1169c1f4dee2fdf281c23d31880991b5a70208b
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-kubernetes
          name: vexxhost/ansible-collection-kubernetes
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        topic: null
      buildset: 5d3526cec66e40c5bb995b0a582d79e3
      buildset_refs:
      - branch: main
        change: '302'
        change_message: "fix(kubernetes): keep role arguments in the stored kubeadm
          configuration\n\nkubeadm only reads `/etc/kubernetes/kubeadm.yaml` for `kubeadm
          init`. `kubeadm join` and `kubeadm upgrade` render the control plane from
          the `ClusterConfiguration` stored in the `kube-system/kubeadm-config` ConfigMap,
          which the role never updates. So anything added to the role's component
          arguments after a cluster was created never reaches it:\n\n- **bind-address**
          ([Zendesk #370829](https://vexxhost.zendesk.com/agent/tickets/370829)):
          clusters created before #121 don't store `bind-address: 0.0.0.0` for kube-scheduler
          and kube-controller-manager. Every upgrade, and every control plane node
          that joins, puts them back on `127.0.0.1`, and their metrics and health
          endpoints stop answering on the node IPs. The customer saw this on a 1.28
          \u2192 1.29 upgrade, and we reproduced it with 3.4.0.\n- **`kubernetes_kubeadm_extra_args`
          (#322)**: overrides for `etcd`, `apiServer`, `controllerManager` and `scheduler`
          only land in the local file, so they never apply to existing clusters, even
          though the defaults say they apply on upgrades.\n\n**This PR**\n\n- Adds
          a `vexxhost.kubernetes.kubeadm_cluster_args` filter. It merges component
          arguments into a `ClusterConfiguration` in the format of the configuration's
          own API version: a mapping before `v1beta4`, a name/value list from it.\n
          \ - Arguments the role sets replace stored ones with the same name, including
          repeated `v1beta4` entries.\n  - Other stored arguments are kept, in order.\n
          \ - `null` removes an argument, the same as in #322, so an override can
          also clean up a stale stored argument such as an old `oidc-username-claim`.\n
          \ - External etcd is left alone.\n- `cluster-configuration.yml` runs right
          after `kubeadm init`, before any node joins and before `kubeadm upgrade
          apply`. On the bootstrap node it reads the ConfigMap with `kubernetes.core.k8s_info`,
          merges `kubernetes_kubeadm_{etcd,api_server,controller_manager,scheduler}_args`,
          and writes it back with `kubernetes.core.k8s` only when the parsed configuration
          changes. A cluster the role just created already matches, so it is left
          alone, and check mode reports the change without writing it.\n- `control-plane.yml`
          now installs the Python `kubernetes` package before bootstrapping, so those
          modules also work on a new cluster's first run. The two install blocks are
          moved, not changed.\n- kubeadm applies the stored arguments the next time
          it writes the components, during an upgrade or a control plane join. Running
          the role doesn't restart anything.\n- Documents this in the role README
          and the `kubernetes_kubeadm_extra_args` defaults comment.\n\n**Behaviour
          change for old clusters:** on their next upgrade, existing clusters get
          every argument a new cluster gets. Besides `bind-address`, clusters created
          before the role set `tls-min-version` (Kubernetes 1.28) will now require
          TLS 1.3 on etcd, the API server, the controller manager and the scheduler.
          Clients that can't do TLS 1.3 would need `tls-min-version: null` in `kubernetes_kubeadm_extra_args`
          for the affected component.\n\n**Validation**\n\n- Unit tests for the filter
          cover both formats, kept and replaced arguments, repeated `v1beta4` entries,
          `null` removal, missing sections, external etcd and idempotence. Role-level
          tests check that a cluster rendered by the role on 1.28, 1.30, 1.31 and
          1.34 comes out unchanged, that old clusters get `bind-address` back, and
          that `kubernetes_kubeadm_extra_args` overrides reach the stored copy. All
          114 unit tests pass, along with pre-commit (including ansible-lint).\n-
          Ran `cluster-configuration.yml` with `ansible-playbook` against a local
          kube-apiserver (envtest 1.34.1), with `kubernetes.core` 2.4.2 and 6.6.0,
          for a stored `v1beta4` config (1.33) and a `v1beta3` config (1.28), both
          missing `bind-address`. The first run added `bind-address: 0.0.0.0` and
          kept the other stored settings and the ConfigMap's other keys. The second
          run skipped the write. Check mode reported the change and left the ConfigMap
          untouched.\n- `kubeadm config validate` (1.34.0 and 1.29.15) accepts both
          merged configurations. `kubeadm init phase control-plane {scheduler,controller-manager}
          --dry-run` (1.34.0) renders `--bind-address=0.0.0.0` from the merged `v1beta4`
          config.\n- **CI:** the cluster-upgrade jobs (three controllers, 1.33.4 \u2192
          1.34.0 and 1.30.14 \u2192 1.31.14) now remove `bind-address` from the stored
          configuration after deploying the old version, which reproduces the customer's
          cluster. After the upgrade they check that `/healthz` on ports 10257 and
          10259 answers on every controller's IP.\n\nClusters that already went through
          an upgrade get the corrected configuration stored on the next run, but their
          manifests keep `127.0.0.1` until the next upgrade or a manual fix of the
          static pod manifests.\n\nCloses CLOUD-183.\n"
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/302
        commit_id: e1169c1f4dee2fdf281c23d31880991b5a70208b
        patchset: e1169c1f4dee2fdf281c23d31880991b5a70208b
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-kubernetes
          name: vexxhost/ansible-collection-kubernetes
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        topic: null
      change: '302'
      change_message: "fix(kubernetes): keep role arguments in the stored kubeadm
        configuration\n\nkubeadm only reads `/etc/kubernetes/kubeadm.yaml` for `kubeadm
        init`. `kubeadm join` and `kubeadm upgrade` render the control plane from
        the `ClusterConfiguration` stored in the `kube-system/kubeadm-config` ConfigMap,
        which the role never updates. So anything added to the role's component arguments
        after a cluster was created never reaches it:\n\n- **bind-address** ([Zendesk
        #370829](https://vexxhost.zendesk.com/agent/tickets/370829)): clusters created
        before #121 don't store `bind-address: 0.0.0.0` for kube-scheduler and kube-controller-manager.
        Every upgrade, and every control plane node that joins, puts them back on
        `127.0.0.1`, and their metrics and health endpoints stop answering on the
        node IPs. The customer saw this on a 1.28 \u2192 1.29 upgrade, and we reproduced
        it with 3.4.0.\n- **`kubernetes_kubeadm_extra_args` (#322)**: overrides for
        `etcd`, `apiServer`, `controllerManager` and `scheduler` only land in the
        local file, so they never apply to existing clusters, even though the defaults
        say they apply on upgrades.\n\n**This PR**\n\n- Adds a `vexxhost.kubernetes.kubeadm_cluster_args`
        filter. It merges component arguments into a `ClusterConfiguration` in the
        format of the configuration's own API version: a mapping before `v1beta4`,
        a name/value list from it.\n  - Arguments the role sets replace stored ones
        with the same name, including repeated `v1beta4` entries.\n  - Other stored
        arguments are kept, in order.\n  - `null` removes an argument, the same as
        in #322, so an override can also clean up a stale stored argument such as
        an old `oidc-username-claim`.\n  - External etcd is left alone.\n- `cluster-configuration.yml`
        runs right after `kubeadm init`, before any node joins and before `kubeadm
        upgrade apply`. On the bootstrap node it reads the ConfigMap with `kubernetes.core.k8s_info`,
        merges `kubernetes_kubeadm_{etcd,api_server,controller_manager,scheduler}_args`,
        and writes it back with `kubernetes.core.k8s` only when the parsed configuration
        changes. A cluster the role just created already matches, so it is left alone,
        and check mode reports the change without writing it.\n- `control-plane.yml`
        now installs the Python `kubernetes` package before bootstrapping, so those
        modules also work on a new cluster's first run. The two install blocks are
        moved, not changed.\n- kubeadm applies the stored arguments the next time
        it writes the components, during an upgrade or a control plane join. Running
        the role doesn't restart anything.\n- Documents this in the role README and
        the `kubernetes_kubeadm_extra_args` defaults comment.\n\n**Behaviour change
        for old clusters:** on their next upgrade, existing clusters get every argument
        a new cluster gets. Besides `bind-address`, clusters created before the role
        set `tls-min-version` (Kubernetes 1.28) will now require TLS 1.3 on etcd,
        the API server, the controller manager and the scheduler. Clients that can't
        do TLS 1.3 would need `tls-min-version: null` in `kubernetes_kubeadm_extra_args`
        for the affected component.\n\n**Validation**\n\n- Unit tests for the filter
        cover both formats, kept and replaced arguments, repeated `v1beta4` entries,
        `null` removal, missing sections, external etcd and idempotence. Role-level
        tests check that a cluster rendered by the role on 1.28, 1.30, 1.31 and 1.34
        comes out unchanged, that old clusters get `bind-address` back, and that `kubernetes_kubeadm_extra_args`
        overrides reach the stored copy. All 114 unit tests pass, along with pre-commit
        (including ansible-lint).\n- Ran `cluster-configuration.yml` with `ansible-playbook`
        against a local kube-apiserver (envtest 1.34.1), with `kubernetes.core` 2.4.2
        and 6.6.0, for a stored `v1beta4` config (1.33) and a `v1beta3` config (1.28),
        both missing `bind-address`. The first run added `bind-address: 0.0.0.0` and
        kept the other stored settings and the ConfigMap's other keys. The second
        run skipped the write. Check mode reported the change and left the ConfigMap
        untouched.\n- `kubeadm config validate` (1.34.0 and 1.29.15) accepts both
        merged configurations. `kubeadm init phase control-plane {scheduler,controller-manager}
        --dry-run` (1.34.0) renders `--bind-address=0.0.0.0` from the merged `v1beta4`
        config.\n- **CI:** the cluster-upgrade jobs (three controllers, 1.33.4 \u2192
        1.34.0 and 1.30.14 \u2192 1.31.14) now remove `bind-address` from the stored
        configuration after deploying the old version, which reproduces the customer's
        cluster. After the upgrade they check that `/healthz` on ports 10257 and 10259
        answers on every controller's IP.\n\nClusters that already went through an
        upgrade get the corrected configuration stored on the next run, but their
        manifests keep `127.0.0.1` until the next upgrade or a manual fix of the static
        pod manifests.\n\nCloses CLOUD-183.\n"
      change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/302
      child_jobs: []
      commit_id: e1169c1f4dee2fdf281c23d31880991b5a70208b
      event_id: 581957f0-d3c5-11f1-9ed5-717ffc87e652
      executor:
        hostname: 2d72f0692154
        inventory_file: /var/lib/zuul/builds/310bb293bb874f9daa2c6b6575fb4508/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/310bb293bb874f9daa2c6b6575fb4508/work/logs
        result_data_file: /var/lib/zuul/builds/310bb293bb874f9daa2c6b6575fb4508/work/results.json
        src_root: /var/lib/zuul/builds/310bb293bb874f9daa2c6b6575fb4508/work/src
        work_root: /var/lib/zuul/builds/310bb293bb874f9daa2c6b6575fb4508/work
      include_vars: []
      items:
      - branch: main
        change: '302'
        change_message: "fix(kubernetes): keep role arguments in the stored kubeadm
          configuration\n\nkubeadm only reads `/etc/kubernetes/kubeadm.yaml` for `kubeadm
          init`. `kubeadm join` and `kubeadm upgrade` render the control plane from
          the `ClusterConfiguration` stored in the `kube-system/kubeadm-config` ConfigMap,
          which the role never updates. So anything added to the role's component
          arguments after a cluster was created never reaches it:\n\n- **bind-address**
          ([Zendesk #370829](https://vexxhost.zendesk.com/agent/tickets/370829)):
          clusters created before #121 don't store `bind-address: 0.0.0.0` for kube-scheduler
          and kube-controller-manager. Every upgrade, and every control plane node
          that joins, puts them back on `127.0.0.1`, and their metrics and health
          endpoints stop answering on the node IPs. The customer saw this on a 1.28
          \u2192 1.29 upgrade, and we reproduced it with 3.4.0.\n- **`kubernetes_kubeadm_extra_args`
          (#322)**: overrides for `etcd`, `apiServer`, `controllerManager` and `scheduler`
          only land in the local file, so they never apply to existing clusters, even
          though the defaults say they apply on upgrades.\n\n**This PR**\n\n- Adds
          a `vexxhost.kubernetes.kubeadm_cluster_args` filter. It merges component
          arguments into a `ClusterConfiguration` in the format of the configuration's
          own API version: a mapping before `v1beta4`, a name/value list from it.\n
          \ - Arguments the role sets replace stored ones with the same name, including
          repeated `v1beta4` entries.\n  - Other stored arguments are kept, in order.\n
          \ - `null` removes an argument, the same as in #322, so an override can
          also clean up a stale stored argument such as an old `oidc-username-claim`.\n
          \ - External etcd is left alone.\n- `cluster-configuration.yml` runs right
          after `kubeadm init`, before any node joins and before `kubeadm upgrade
          apply`. On the bootstrap node it reads the ConfigMap with `kubernetes.core.k8s_info`,
          merges `kubernetes_kubeadm_{etcd,api_server,controller_manager,scheduler}_args`,
          and writes it back with `kubernetes.core.k8s` only when the parsed configuration
          changes. A cluster the role just created already matches, so it is left
          alone, and check mode reports the change without writing it.\n- `control-plane.yml`
          now installs the Python `kubernetes` package before bootstrapping, so those
          modules also work on a new cluster's first run. The two install blocks are
          moved, not changed.\n- kubeadm applies the stored arguments the next time
          it writes the components, during an upgrade or a control plane join. Running
          the role doesn't restart anything.\n- Documents this in the role README
          and the `kubernetes_kubeadm_extra_args` defaults comment.\n\n**Behaviour
          change for old clusters:** on their next upgrade, existing clusters get
          every argument a new cluster gets. Besides `bind-address`, clusters created
          before the role set `tls-min-version` (Kubernetes 1.28) will now require
          TLS 1.3 on etcd, the API server, the controller manager and the scheduler.
          Clients that can't do TLS 1.3 would need `tls-min-version: null` in `kubernetes_kubeadm_extra_args`
          for the affected component.\n\n**Validation**\n\n- Unit tests for the filter
          cover both formats, kept and replaced arguments, repeated `v1beta4` entries,
          `null` removal, missing sections, external etcd and idempotence. Role-level
          tests check that a cluster rendered by the role on 1.28, 1.30, 1.31 and
          1.34 comes out unchanged, that old clusters get `bind-address` back, and
          that `kubernetes_kubeadm_extra_args` overrides reach the stored copy. All
          114 unit tests pass, along with pre-commit (including ansible-lint).\n-
          Ran `cluster-configuration.yml` with `ansible-playbook` against a local
          kube-apiserver (envtest 1.34.1), with `kubernetes.core` 2.4.2 and 6.6.0,
          for a stored `v1beta4` config (1.33) and a `v1beta3` config (1.28), both
          missing `bind-address`. The first run added `bind-address: 0.0.0.0` and
          kept the other stored settings and the ConfigMap's other keys. The second
          run skipped the write. Check mode reported the change and left the ConfigMap
          untouched.\n- `kubeadm config validate` (1.34.0 and 1.29.15) accepts both
          merged configurations. `kubeadm init phase control-plane {scheduler,controller-manager}
          --dry-run` (1.34.0) renders `--bind-address=0.0.0.0` from the merged `v1beta4`
          config.\n- **CI:** the cluster-upgrade jobs (three controllers, 1.33.4 \u2192
          1.34.0 and 1.30.14 \u2192 1.31.14) now remove `bind-address` from the stored
          configuration after deploying the old version, which reproduces the customer's
          cluster. After the upgrade they check that `/healthz` on ports 10257 and
          10259 answers on every controller's IP.\n\nClusters that already went through
          an upgrade get the corrected configuration stored on the next run, but their
          manifests keep `127.0.0.1` until the next upgrade or a manual fix of the
          static pod manifests.\n\nCloses CLOUD-183.\n"
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/302
        commit_id: e1169c1f4dee2fdf281c23d31880991b5a70208b
        patchset: e1169c1f4dee2fdf281c23d31880991b5a70208b
        project:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-kubernetes
          name: vexxhost/ansible-collection-kubernetes
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
        topic: null
      job: ansible-collection-kubernetes-molecule-download-binaries
      jobtags: []
      max_attempts: 3
      message: Zml4KGt1YmVybmV0ZXMpOiBrZWVwIHJvbGUgYXJndW1lbnRzIGluIHRoZSBzdG9yZWQga3ViZWFkbSBjb25maWd1cmF0aW9uCgprdWJlYWRtIG9ubHkgcmVhZHMgYC9ldGMva3ViZXJuZXRlcy9rdWJlYWRtLnlhbWxgIGZvciBga3ViZWFkbSBpbml0YC4gYGt1YmVhZG0gam9pbmAgYW5kIGBrdWJlYWRtIHVwZ3JhZGVgIHJlbmRlciB0aGUgY29udHJvbCBwbGFuZSBmcm9tIHRoZSBgQ2x1c3RlckNvbmZpZ3VyYXRpb25gIHN0b3JlZCBpbiB0aGUgYGt1YmUtc3lzdGVtL2t1YmVhZG0tY29uZmlnYCBDb25maWdNYXAsIHdoaWNoIHRoZSByb2xlIG5ldmVyIHVwZGF0ZXMuIFNvIGFueXRoaW5nIGFkZGVkIHRvIHRoZSByb2xlJ3MgY29tcG9uZW50IGFyZ3VtZW50cyBhZnRlciBhIGNsdXN0ZXIgd2FzIGNyZWF0ZWQgbmV2ZXIgcmVhY2hlcyBpdDoKCi0gKipiaW5kLWFkZHJlc3MqKiAoW1plbmRlc2sgIzM3MDgyOV0oaHR0cHM6Ly92ZXh4aG9zdC56ZW5kZXNrLmNvbS9hZ2VudC90aWNrZXRzLzM3MDgyOSkpOiBjbHVzdGVycyBjcmVhdGVkIGJlZm9yZSAjMTIxIGRvbid0IHN0b3JlIGBiaW5kLWFkZHJlc3M6IDAuMC4wLjBgIGZvciBrdWJlLXNjaGVkdWxlciBhbmQga3ViZS1jb250cm9sbGVyLW1hbmFnZXIuIEV2ZXJ5IHVwZ3JhZGUsIGFuZCBldmVyeSBjb250cm9sIHBsYW5lIG5vZGUgdGhhdCBqb2lucywgcHV0cyB0aGVtIGJhY2sgb24gYDEyNy4wLjAuMWAsIGFuZCB0aGVpciBtZXRyaWNzIGFuZCBoZWFsdGggZW5kcG9pbnRzIHN0b3AgYW5zd2VyaW5nIG9uIHRoZSBub2RlIElQcy4gVGhlIGN1c3RvbWVyIHNhdyB0aGlzIG9uIGEgMS4yOCDihpIgMS4yOSB1cGdyYWRlLCBhbmQgd2UgcmVwcm9kdWNlZCBpdCB3aXRoIDMuNC4wLgotICoqYGt1YmVybmV0ZXNfa3ViZWFkbV9leHRyYV9hcmdzYCAoIzMyMikqKjogb3ZlcnJpZGVzIGZvciBgZXRjZGAsIGBhcGlTZXJ2ZXJgLCBgY29udHJvbGxlck1hbmFnZXJgIGFuZCBgc2NoZWR1bGVyYCBvbmx5IGxhbmQgaW4gdGhlIGxvY2FsIGZpbGUsIHNvIHRoZXkgbmV2ZXIgYXBwbHkgdG8gZXhpc3RpbmcgY2x1c3RlcnMsIGV2ZW4gdGhvdWdoIHRoZSBkZWZhdWx0cyBzYXkgdGhleSBhcHBseSBvbiB1cGdyYWRlcy4KCioqVGhpcyBQUioqCgotIEFkZHMgYSBgdmV4eGhvc3Qua3ViZXJuZXRlcy5rdWJlYWRtX2NsdXN0ZXJfYXJnc2AgZmlsdGVyLiBJdCBtZXJnZXMgY29tcG9uZW50IGFyZ3VtZW50cyBpbnRvIGEgYENsdXN0ZXJDb25maWd1cmF0aW9uYCBpbiB0aGUgZm9ybWF0IG9mIHRoZSBjb25maWd1cmF0aW9uJ3Mgb3duIEFQSSB2ZXJzaW9uOiBhIG1hcHBpbmcgYmVmb3JlIGB2MWJldGE0YCwgYSBuYW1lL3ZhbHVlIGxpc3QgZnJvbSBpdC4KICAtIEFyZ3VtZW50cyB0aGUgcm9sZSBzZXRzIHJlcGxhY2Ugc3RvcmVkIG9uZXMgd2l0aCB0aGUgc2FtZSBuYW1lLCBpbmNsdWRpbmcgcmVwZWF0ZWQgYHYxYmV0YTRgIGVudHJpZXMuCiAgLSBPdGhlciBzdG9yZWQgYXJndW1lbnRzIGFyZSBrZXB0LCBpbiBvcmRlci4KICAtIGBudWxsYCByZW1vdmVzIGFuIGFyZ3VtZW50LCB0aGUgc2FtZSBhcyBpbiAjMzIyLCBzbyBhbiBvdmVycmlkZSBjYW4gYWxzbyBjbGVhbiB1cCBhIHN0YWxlIHN0b3JlZCBhcmd1bWVudCBzdWNoIGFzIGFuIG9sZCBgb2lkYy11c2VybmFtZS1jbGFpbWAuCiAgLSBFeHRlcm5hbCBldGNkIGlzIGxlZnQgYWxvbmUuCi0gYGNsdXN0ZXItY29uZmlndXJhdGlvbi55bWxgIHJ1bnMgcmlnaHQgYWZ0ZXIgYGt1YmVhZG0gaW5pdGAsIGJlZm9yZSBhbnkgbm9kZSBqb2lucyBhbmQgYmVmb3JlIGBrdWJlYWRtIHVwZ3JhZGUgYXBwbHlgLiBPbiB0aGUgYm9vdHN0cmFwIG5vZGUgaXQgcmVhZHMgdGhlIENvbmZpZ01hcCB3aXRoIGBrdWJlcm5ldGVzLmNvcmUuazhzX2luZm9gLCBtZXJnZXMgYGt1YmVybmV0ZXNfa3ViZWFkbV97ZXRjZCxhcGlfc2VydmVyLGNvbnRyb2xsZXJfbWFuYWdlcixzY2hlZHVsZXJ9X2FyZ3NgLCBhbmQgd3JpdGVzIGl0IGJhY2sgd2l0aCBga3ViZXJuZXRlcy5jb3JlLms4c2Agb25seSB3aGVuIHRoZSBwYXJzZWQgY29uZmlndXJhdGlvbiBjaGFuZ2VzLiBBIGNsdXN0ZXIgdGhlIHJvbGUganVzdCBjcmVhdGVkIGFscmVhZHkgbWF0Y2hlcywgc28gaXQgaXMgbGVmdCBhbG9uZSwgYW5kIGNoZWNrIG1vZGUgcmVwb3J0cyB0aGUgY2hhbmdlIHdpdGhvdXQgd3JpdGluZyBpdC4KLSBgY29udHJvbC1wbGFuZS55bWxgIG5vdyBpbnN0YWxscyB0aGUgUHl0aG9uIGBrdWJlcm5ldGVzYCBwYWNrYWdlIGJlZm9yZSBib290c3RyYXBwaW5nLCBzbyB0aG9zZSBtb2R1bGVzIGFsc28gd29yayBvbiBhIG5ldyBjbHVzdGVyJ3MgZmlyc3QgcnVuLiBUaGUgdHdvIGluc3RhbGwgYmxvY2tzIGFyZSBtb3ZlZCwgbm90IGNoYW5nZWQuCi0ga3ViZWFkbSBhcHBsaWVzIHRoZSBzdG9yZWQgYXJndW1lbnRzIHRoZSBuZXh0IHRpbWUgaXQgd3JpdGVzIHRoZSBjb21wb25lbnRzLCBkdXJpbmcgYW4gdXBncmFkZSBvciBhIGNvbnRyb2wgcGxhbmUgam9pbi4gUnVubmluZyB0aGUgcm9sZSBkb2Vzbid0IHJlc3RhcnQgYW55dGhpbmcuCi0gRG9jdW1lbnRzIHRoaXMgaW4gdGhlIHJvbGUgUkVBRE1FIGFuZCB0aGUgYGt1YmVybmV0ZXNfa3ViZWFkbV9leHRyYV9hcmdzYCBkZWZhdWx0cyBjb21tZW50LgoKKipCZWhhdmlvdXIgY2hhbmdlIGZvciBvbGQgY2x1c3RlcnM6Kiogb24gdGhlaXIgbmV4dCB1cGdyYWRlLCBleGlzdGluZyBjbHVzdGVycyBnZXQgZXZlcnkgYXJndW1lbnQgYSBuZXcgY2x1c3RlciBnZXRzLiBCZXNpZGVzIGBiaW5kLWFkZHJlc3NgLCBjbHVzdGVycyBjcmVhdGVkIGJlZm9yZSB0aGUgcm9sZSBzZXQgYHRscy1taW4tdmVyc2lvbmAgKEt1YmVybmV0ZXMgMS4yOCkgd2lsbCBub3cgcmVxdWlyZSBUTFMgMS4zIG9uIGV0Y2QsIHRoZSBBUEkgc2VydmVyLCB0aGUgY29udHJvbGxlciBtYW5hZ2VyIGFuZCB0aGUgc2NoZWR1bGVyLiBDbGllbnRzIHRoYXQgY2FuJ3QgZG8gVExTIDEuMyB3b3VsZCBuZWVkIGB0bHMtbWluLXZlcnNpb246IG51bGxgIGluIGBrdWJlcm5ldGVzX2t1YmVhZG1fZXh0cmFfYXJnc2AgZm9yIHRoZSBhZmZlY3RlZCBjb21wb25lbnQuCgoqKlZhbGlkYXRpb24qKgoKLSBVbml0IHRlc3RzIGZvciB0aGUgZmlsdGVyIGNvdmVyIGJvdGggZm9ybWF0cywga2VwdCBhbmQgcmVwbGFjZWQgYXJndW1lbnRzLCByZXBlYXRlZCBgdjFiZXRhNGAgZW50cmllcywgYG51bGxgIHJlbW92YWwsIG1pc3Npbmcgc2VjdGlvbnMsIGV4dGVybmFsIGV0Y2QgYW5kIGlkZW1wb3RlbmNlLiBSb2xlLWxldmVsIHRlc3RzIGNoZWNrIHRoYXQgYSBjbHVzdGVyIHJlbmRlcmVkIGJ5IHRoZSByb2xlIG9uIDEuMjgsIDEuMzAsIDEuMzEgYW5kIDEuMzQgY29tZXMgb3V0IHVuY2hhbmdlZCwgdGhhdCBvbGQgY2x1c3RlcnMgZ2V0IGBiaW5kLWFkZHJlc3NgIGJhY2ssIGFuZCB0aGF0IGBrdWJlcm5ldGVzX2t1YmVhZG1fZXh0cmFfYXJnc2Agb3ZlcnJpZGVzIHJlYWNoIHRoZSBzdG9yZWQgY29weS4gQWxsIDExNCB1bml0IHRlc3RzIHBhc3MsIGFsb25nIHdpdGggcHJlLWNvbW1pdCAoaW5jbHVkaW5nIGFuc2libGUtbGludCkuCi0gUmFuIGBjbHVzdGVyLWNvbmZpZ3VyYXRpb24ueW1sYCB3aXRoIGBhbnNpYmxlLXBsYXlib29rYCBhZ2FpbnN0IGEgbG9jYWwga3ViZS1hcGlzZXJ2ZXIgKGVudnRlc3QgMS4zNC4xKSwgd2l0aCBga3ViZXJuZXRlcy5jb3JlYCAyLjQuMiBhbmQgNi42LjAsIGZvciBhIHN0b3JlZCBgdjFiZXRhNGAgY29uZmlnICgxLjMzKSBhbmQgYSBgdjFiZXRhM2AgY29uZmlnICgxLjI4KSwgYm90aCBtaXNzaW5nIGBiaW5kLWFkZHJlc3NgLiBUaGUgZmlyc3QgcnVuIGFkZGVkIGBiaW5kLWFkZHJlc3M6IDAuMC4wLjBgIGFuZCBrZXB0IHRoZSBvdGhlciBzdG9yZWQgc2V0dGluZ3MgYW5kIHRoZSBDb25maWdNYXAncyBvdGhlciBrZXlzLiBUaGUgc2Vjb25kIHJ1biBza2lwcGVkIHRoZSB3cml0ZS4gQ2hlY2sgbW9kZSByZXBvcnRlZCB0aGUgY2hhbmdlIGFuZCBsZWZ0IHRoZSBDb25maWdNYXAgdW50b3VjaGVkLgotIGBrdWJlYWRtIGNvbmZpZyB2YWxpZGF0ZWAgKDEuMzQuMCBhbmQgMS4yOS4xNSkgYWNjZXB0cyBib3RoIG1lcmdlZCBjb25maWd1cmF0aW9ucy4gYGt1YmVhZG0gaW5pdCBwaGFzZSBjb250cm9sLXBsYW5lIHtzY2hlZHVsZXIsY29udHJvbGxlci1tYW5hZ2VyfSAtLWRyeS1ydW5gICgxLjM0LjApIHJlbmRlcnMgYC0tYmluZC1hZGRyZXNzPTAuMC4wLjBgIGZyb20gdGhlIG1lcmdlZCBgdjFiZXRhNGAgY29uZmlnLgotICoqQ0k6KiogdGhlIGNsdXN0ZXItdXBncmFkZSBqb2JzICh0aHJlZSBjb250cm9sbGVycywgMS4zMy40IOKGkiAxLjM0LjAgYW5kIDEuMzAuMTQg4oaSIDEuMzEuMTQpIG5vdyByZW1vdmUgYGJpbmQtYWRkcmVzc2AgZnJvbSB0aGUgc3RvcmVkIGNvbmZpZ3VyYXRpb24gYWZ0ZXIgZGVwbG95aW5nIHRoZSBvbGQgdmVyc2lvbiwgd2hpY2ggcmVwcm9kdWNlcyB0aGUgY3VzdG9tZXIncyBjbHVzdGVyLiBBZnRlciB0aGUgdXBncmFkZSB0aGV5IGNoZWNrIHRoYXQgYC9oZWFsdGh6YCBvbiBwb3J0cyAxMDI1NyBhbmQgMTAyNTkgYW5zd2VycyBvbiBldmVyeSBjb250cm9sbGVyJ3MgSVAuCgpDbHVzdGVycyB0aGF0IGFscmVhZHkgd2VudCB0aHJvdWdoIGFuIHVwZ3JhZGUgZ2V0IHRoZSBjb3JyZWN0ZWQgY29uZmlndXJhdGlvbiBzdG9yZWQgb24gdGhlIG5leHQgcnVuLCBidXQgdGhlaXIgbWFuaWZlc3RzIGtlZXAgYDEyNy4wLjAuMWAgdW50aWwgdGhlIG5leHQgdXBncmFkZSBvciBhIG1hbnVhbCBmaXggb2YgdGhlIHN0YXRpYyBwb2QgbWFuaWZlc3RzLgoKQ2xvc2VzIENMT1VELTE4My4K
      patchset: e1169c1f4dee2fdf281c23d31880991b5a70208b
      pipeline: check
      playbook_context:
        playbook_projects:
          trusted/project_0/github.com/vexxhost/zuul-config:
            canonical_name: github.com/vexxhost/zuul-config
            checkout: main
            commit: 298983cd1253e6833abdb49d87d912527e0e6597
          trusted/project_1/opendev.org/zuul/zuul-jobs:
            canonical_name: opendev.org/zuul/zuul-jobs
            checkout: master
            commit: f440b84a5acad7dc4611f363d8aca14806971959
          trusted/project_2/github.com/vexxhost/zuul-jobs:
            canonical_name: github.com/vexxhost/zuul-jobs
            checkout: main
            commit: 4fd48825891421af0774bdd500fee36e111d80a6
          untrusted/project_0/github.com/vexxhost/zuul-jobs:
            canonical_name: github.com/vexxhost/zuul-jobs
            checkout: main
            commit: 4fd48825891421af0774bdd500fee36e111d80a6
          untrusted/project_1/github.com/vexxhost/zuul-config:
            canonical_name: github.com/vexxhost/zuul-config
            checkout: main
            commit: 298983cd1253e6833abdb49d87d912527e0e6597
          untrusted/project_2/opendev.org/zuul/zuul-jobs:
            canonical_name: opendev.org/zuul/zuul-jobs
            checkout: master
            commit: f440b84a5acad7dc4611f363d8aca14806971959
          untrusted/project_3/github.com/vexxhost/ansible-collection-kubernetes:
            canonical_name: github.com/vexxhost/ansible-collection-kubernetes
            checkout: main
            commit: 88fdb40def7055e11132b9378c2948fb018139dd
          untrusted/project_4/opendev.org/openstack/openstack-helm:
            canonical_name: opendev.org/openstack/openstack-helm
            checkout: master
            commit: 0028e05c0fff162c25201143e9d13dfd7245f401
        playbooks:
        - path: untrusted/project_0/github.com/vexxhost/zuul-jobs/playbooks/molecule/run.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/playbook_0/role_1/zuul-jobs
            link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs
            role_path: ansible/playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/playbook_0/role_2/zuul-jobs
            link_target: untrusted/project_0/github.com/vexxhost/zuul-jobs
            role_path: ansible/playbook_0/role_2/zuul-jobs/roles
        post_playbooks:
        - path: untrusted/project_3/github.com/vexxhost/ansible-collection-kubernetes/test-playbooks/molecule/post.yml
          roles:
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/post_playbook_0/role_0/collection-kubernetes
            link_target: untrusted/project_3/github.com/vexxhost/ansible-collection-kubernetes
            role_path: ansible/post_playbook_0/role_0/collection-kubernetes/roles
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/post_playbook_0/role_1/openstack-helm
            link_target: untrusted/project_4/opendev.org/openstack/openstack-helm
            role_path: ansible/post_playbook_0/role_1/openstack-helm/roles
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/post_playbook_0/role_3/zuul-jobs
            link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_0/role_3/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_0/role_4/zuul-jobs
            link_target: untrusted/project_0/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_0/role_4/zuul-jobs/roles
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/post.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/post_playbook_1/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_1/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_1/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_1/role_2/zuul-jobs/roles
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/post-logs.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/post_playbook_2/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/post_playbook_2/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/post_playbook_2/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/post_playbook_2/role_2/zuul-jobs/roles
        pre_playbooks:
        - path: trusted/project_0/github.com/vexxhost/zuul-config/playbooks/base/pre.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_0/role_1/zuul-jobs
            link_target: trusted/project_1/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_0/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/pre_playbook_0/role_2/zuul-jobs
            link_target: trusted/project_2/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_0/role_2/zuul-jobs/roles
        - path: untrusted/project_0/github.com/vexxhost/zuul-jobs/playbooks/molecule/pre.yaml
          roles:
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_1/role_1/zuul-jobs
            link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_1/role_1/zuul-jobs/roles
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/pre_playbook_1/role_2/zuul-jobs
            link_target: untrusted/project_0/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_1/role_2/zuul-jobs/roles
        - path: untrusted/project_3/github.com/vexxhost/ansible-collection-kubernetes/test-playbooks/molecule/pre.yml
          roles:
          - checkout: main
            checkout_description: playbook branch
            link_name: ansible/pre_playbook_2/role_0/collection-kubernetes
            link_target: untrusted/project_3/github.com/vexxhost/ansible-collection-kubernetes
            role_path: ansible/pre_playbook_2/role_0/collection-kubernetes/roles
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_2/role_1/openstack-helm
            link_target: untrusted/project_4/opendev.org/openstack/openstack-helm
            role_path: ansible/pre_playbook_2/role_1/openstack-helm/roles
          - checkout: master
            checkout_description: project default branch
            link_name: ansible/pre_playbook_2/role_3/zuul-jobs
            link_target: untrusted/project_2/opendev.org/zuul/zuul-jobs
            role_path: ansible/pre_playbook_2/role_3/zuul-jobs/roles
          - checkout: main
            checkout_description: zuul branch
            link_name: ansible/pre_playbook_2/role_4/zuul-jobs
            link_target: untrusted/project_0/github.com/vexxhost/zuul-jobs
            role_path: ansible/pre_playbook_2/role_4/zuul-jobs/roles
      post_review: false
      post_timeout: null
      pre_timeout: null
      project:
        canonical_hostname: github.com
        canonical_name: github.com/vexxhost/ansible-collection-kubernetes
        name: vexxhost/ansible-collection-kubernetes
        short_name: ansible-collection-kubernetes
        src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
      projects:
        github.com/ansible-collections/ansible.posix:
          canonical_hostname: github.com
          canonical_name: github.com/ansible-collections/ansible.posix
          checkout: main
          checkout_description: zuul branch
          commit: 0f4453f85ee993687a4cab860e3b55438144f920
          name: ansible-collections/ansible.posix
          required: true
          short_name: ansible.posix
          src_dir: src/github.com/ansible-collections/ansible.posix
        github.com/ansible-collections/community.crypto:
          canonical_hostname: github.com
          canonical_name: github.com/ansible-collections/community.crypto
          checkout: main
          checkout_description: zuul branch
          commit: 1bdefe5f420bb2d38cf92ea109ca39e1d4372347
          name: ansible-collections/community.crypto
          required: true
          short_name: community.crypto
          src_dir: src/github.com/ansible-collections/community.crypto
        github.com/ansible-collections/community.general:
          canonical_hostname: github.com
          canonical_name: github.com/ansible-collections/community.general
          checkout: main
          checkout_description: zuul branch
          commit: f71f1b4ced1137a5aaf3c9f71be76b7523796216
          name: ansible-collections/community.general
          required: true
          short_name: community.general
          src_dir: src/github.com/ansible-collections/community.general
        github.com/ansible-collections/community.library_inventory_filtering:
          canonical_hostname: github.com
          canonical_name: github.com/ansible-collections/community.library_inventory_filtering
          checkout: stable-1
          checkout_description: project default branch
          commit: 90cd245b3acbab4089041f36c5e83dd8081eae4e
          name: ansible-collections/community.library_inventory_filtering
          required: true
          short_name: community.library_inventory_filtering
          src_dir: src/github.com/ansible-collections/community.library_inventory_filtering
        github.com/ansible-collections/kubernetes.core:
          canonical_hostname: github.com
          canonical_name: github.com/ansible-collections/kubernetes.core
          checkout: main
          checkout_description: zuul branch
          commit: 782672d2fdb0004d593440a3ddd4b9db014d9e4b
          name: ansible-collections/kubernetes.core
          required: true
          short_name: kubernetes.core
          src_dir: src/github.com/ansible-collections/kubernetes.core
        github.com/vexxhost/ansible-collection-containers:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-containers
          checkout: main
          checkout_description: zuul branch
          commit: d22923ebd40c0fd5a345318c1db90d125fb5140f
          name: vexxhost/ansible-collection-containers
          required: true
          short_name: ansible-collection-containers
          src_dir: src/github.com/vexxhost/ansible-collection-containers
        github.com/vexxhost/ansible-collection-kubernetes:
          canonical_hostname: github.com
          canonical_name: github.com/vexxhost/ansible-collection-kubernetes
          checkout: main
          checkout_description: zuul branch
          commit: 88fdb40def7055e11132b9378c2948fb018139dd
          name: vexxhost/ansible-collection-kubernetes
          required: false
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
      ref: refs/pull/302/head
      resources: {}
      tenant: oss
      timeout: 1800
      topic: null
      voting: true
