all:
  children:
    controllers:
      hosts:
        controller: null
    zuul_unreachable:
      hosts: {}
  hosts:
    controller:
      ansible_connection: ssh
      ansible_host: 162.253.55.44
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      cilium_helm_values:
        operator:
          replicas: 1
      cilium_ipv4_cidr: 172.24.0.0/16
      cluster_api_addon_providers:
      - name: csr-approver
        version: 0.1.0
      cluster_api_infrastructure_provider: openstack
      cluster_api_infrastructure_version: 0.14.4
      cluster_api_node_selector:
        kubernetes.io/os: linux
      cluster_api_version: 1.13.2
      clusterctl_version: 1.13.2
      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: cluster-api
      nodepool:
        az: yul2
        cloud: public
        external_id: d6573e4e-303c-4472-9178-c016fa6fc748
        host_id: a01cb4e3d8698a10b6af7a23bf700f5af12859fba177738e8fa3822e
        interface_ip: 162.253.55.44
        label: debian-trixie
        node_properties: {}
        private_ipv4: 162.253.55.44
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.44
        public_ipv6: 2604:e100:1:0:f816:3eff:fec0:9539
        region: ca-ymq-1
        slot: null
      zuul_node:
        az: yul2
        cloud: public
        external_id: d6573e4e-303c-4472-9178-c016fa6fc748
        host_id: a01cb4e3d8698a10b6af7a23bf700f5af12859fba177738e8fa3822e
        interface_ip: 162.253.55.44
        label: debian-trixie
        node_properties: {}
        private_ipv4: 162.253.55.44
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.44
        public_ipv6: 2604:e100:1:0:f816:3eff:fec0:9539
        region: ca-ymq-1
        slot: null
        uuid: null
  vars:
    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: cluster-api
    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-cluster-api explicit: None implied:
        {MatchAny:{ImpliedBranchMatcher:main}} source: vexxhost/ansible-collection-kubernetes/.zuul.yaml@main#128>'
      - '<Job ansible-collection-kubernetes-molecule-cluster-api explicit: None implied:
        None source: vexxhost/ansible-collection-kubernetes/.zuul.yaml@main#247>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: fc433883fbfc40d697c9eaacf906451c
      build_refs:
      - branch: main
        change: '348'
        change_message: 'fix(kubernetes): guard resize without pod QoS cgroups


          ## ENG-219: guard in-place resize without pod QoS cgroups


          ### Problem


          Older collection releases joined kubelets with:


          ```text

          --cgroups-per-qos=false --enforce-node-allocatable=

          ```


          Kubeadm preserves those arguments in `/var/lib/kubelet/kubeadm-flags.env`
          across upgrades. A cluster can therefore reach Kubernetes 1.35 or later
          while some kubelets still run without pod QoS cgroups.


          Kubernetes 1.35 made in-place pod resize generally available. On an affected
          node, a resize can reach a nil pod-cgroup configuration and crash the kubelet,
          as described in [kubernetes/kubernetes#137993](https://github.com/kubernetes/kubernetes/issues/137993).
          The upstream correction is tracked by [kubernetes/kubernetes#137999](https://github.com/kubernetes/kubernetes/pull/137999).


          There are two trigger paths:


          1. **API-initiated resize:** an API client updates `pods/resize`; admission
          can block this path.

          2. **Kubelet-initiated reconciliation:** releases containing the behavior
          from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387)
          can reach the vulnerable path internally; admission cannot intercept it.


          ### Safety model


          This change adds two protections:


          - A hard per-minor version denylist for releases where kubelet-initiated
          reconciliation can trigger the panic.

          - A `ValidatingAdmissionPolicy` and binding for affected releases where
          API-initiated resize remains the trigger.


          The policy:


          - matches only `UPDATE` requests to the core `v1` `pods/resize` subresource;

          - leaves ordinary Pod updates unaffected;

          - uses `failurePolicy: Fail`;

          - creates the policy before its binding;

          - deletes the binding before the policy;

          - remains installed while any affected kubelet lacks pod QoS cgroups or
          safety evidence is incomplete.


          On a new cluster, the guard is applied immediately after the first API server
          becomes available and before additional control-plane or worker nodes join.
          On an existing cluster, it is applied before joins and before any kubelet
          upgrade to 1.35+.


          Creating the policy objects is not treated as proof of enforcement. After
          creating the policy and binding, the role generates a unique probe name
          on the Ansible controller before submitting the Pod create request. The
          name therefore remains available to the `always` cleanup even if the API
          server commits the create but the client loses the response. EndpointSlice
          discovery retries until it finds a ready endpoint with an address and a
          non-null HTTPS port. The role then waits until every discovered ready API
          server can read the probe and sends a server-side dry-run `pods/resize`
          request directly to every server. Success requires a nonzero response containing
          both `ValidatingAdmissionPolicy ''<managed-name>''` and the exact managed
          validation message. Generic Pod errors and denials from another policy remain
          failures, and retry exhaustion stops the play. Cleanup targets only the
          pre-generated name from this invocation before joins or upgrades can continue.


          ### Cluster-wide inspection


          The preflight uses the Kubernetes API as the primary source of effective
          state:


          - `status.nodeInfo.kubeletVersion` provides the running kubelet version.

          - `/api/v1/nodes/<name>/proxy/configz` provides effective `cgroupsPerQOS`,
          including command-line overrides.

          - Every Node returned by the API is inspected, including Nodes no longer
          represented in Ansible inventory.


          An explicitly configured `kubernetes_bootstrap_node` is tried first, followed
          by every control-plane host. Transport failures and delegate-wide `api_error`
          results fall through to the next controller. Results with node-local `configz`
          errors are retained as a conservative fallback while later controllers are
          tried for complete evidence.


          For a play host with no Node object, local kubelet flags and configuration
          are inspected. Failed reads remain unknown; only a successfully confirmed
          absent file permits inventory/default evidence.


          API inspection, untracked-Node classification, and the final safety decision
          are calculated once on a designated fact host. The resulting facts are then
          explicitly published to every active play host before the Kubernetes role
          continues. A denylisted target fails cluster-wide with `any_errors_fatal`.


          If no controller can enumerate Nodes, local host inspection is insufficient
          to prove that no out-of-inventory Nodes exist. The role therefore records
          a cluster-level unknown, retains the admission guard, and rejects denylisted
          targets. File absence is not accepted as cluster-history evidence because
          reset or replacement hosts can lack kubelet state while an older out-of-inventory
          Node remains active.


          The API-enumeration exception is available only when an operator explicitly
          sets `kubernetes_upgrade_check_assert_fresh_bootstrap: true` for the first
          bootstrap of a cluster. It defaults to false and is honored only when the
          complete Kubernetes inventory is present in the play, every play host can
          be checked, and every host lacks `/etc/kubernetes/kubelet.conf`. An existing
          marker, failed read, or unreachable host rejects a stale assertion. The
          assertion is documented as a one-run `--extra-vars` value and must not be
          persisted in inventory or used for recovery, reset, replacement, or rejoin
          operations. Failed API enumeration in a limited play does not open Ansible
          connections to hosts outside that play.


          ### Policy lifecycle


          The collection manages:


          ```text

          ValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard

          ValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard

          ```


          The guard is required when:


          - the target version is in an affected resize range and any inventory or
          API-only Node lacks pod QoS cgroups;

          - an installed kubelet on a legacy node remains in an affected range;

          - a Node has unknown QoS-cgroup or installed-version state; or

          - complete API Node enumeration cannot be established on an existing cluster.


          It is removed only when complete evidence shows that no affected kubelet
          remains vulnerable. Per-minor ranges allow each Kubernetes branch to be
          opened independently when the upstream fix is released.


          ### Migration workflow


          `docs/ops/qos-cgroups.md` documents the permanent remediation:


          - migrate one node at a time, workers before control-plane nodes;

          - preserve workload and stacked-etcd quorum;

          - drain, reset, delete the old Node object, and rejoin instead of editing
          kubelet flags in place;

          - register the replacement with a temporary `NoSchedule` taint so it is
          protected from its first API registration;

          - keep the taint through kubelet, `configz`, runtime-driver, workload, and
          control-plane health validation;

          - remove the taint only after every applicable check passes;

          - keep the migration separate from the Kubernetes version upgrade.


          The runbook also refreshes the shared kubelet ConfigMap before rejoin and
          verifies kubelet/containerd cgroup-driver agreement.


          ### CI coverage


          Two voting Zuul scenarios run in both check and gate:


          - `cluster-upgrade-resize-guard` performs a `1.34.9 -> 1.35.6` upgrade from
          legacy QoS-cgroup-disabled nodes and runs the enforcement barrier before
          the upgrade. It verifies policy enforcement, probe cleanup, ordinary Pod
          updates, denied resize behavior, kubelet health, and upgrade canaries.

          - `cluster-upgrade-resize-cleanup` seeds stale policy and binding resources
          on a QoS-enabled cluster and verifies their actual removal. It skips only
          the unrelated Cilium restart assertion that keeps the generic upgrade job
          non-voting.


          ### Validation


          - `231` unit tests pass.

          - Full pre-commit, Black, Flake8, isort, YAML lint, and Ansible lint pass.

          - `ansible-test sanity --test validate-modules plugins/modules/kubelet_configz.py`
          passes. The new module uses the required GPLv3 header, and the module and
          new `version_matching_ranges` filter declare `version_added: 3.6.0`.

          - `git diff --check` passes.

          - A read-only multi-host rehearsal forced the preferred API delegate to
          be unreachable, retried a healthy controller, enumerated all Nodes, and
          verified identical safety facts on every play host.

          - A second read-only multi-host rehearsal forced every selected delegate
          to return no usable API enumeration and verified every play host retained
          the guard through the same cluster-level unknown result. Regression coverage
          additionally verifies that freshness requires an explicit full-inventory
          assertion and that failed API enumeration performs no inventory-wide marker
          probe.

          - Both rehearsals completed with `changed=0`, `unreachable=0`, and `failed=0`.

          - A live Kubernetes `1.36.2` rehearsal verified controller-side probe-name
          generation, ready-HTTPS EndpointSlice discovery, and the exact managed-policy
          signature and validation message directly through all three API servers.
          The generated probe was visible through every endpoint, was removed by its
          pre-generated name, and the existing-guard run completed with `changed=0`,
          `unreachable=0`, and `failed=0`.

          - Failure-path rehearsals proved that Pod `NotFound`, an invalid assigned
          Node, and denials from a different policy exhaust retries and end with `failed=1`.
          In the new-policy propagation rehearsal, one API server observed the temporary
          policy while two still returned the pre-existing policy; the barrier correctly
          refused to continue and the `always` cleanup removed the generated probe
          and temporary policy resources.

          - The pre-existing guard remained installed, no generated probe Pods remained,
          and every node remained `Ready` after the rehearsals.

          '
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/348
        commit_id: 01fd7abb7e01e8cc2214be6ba57343b95f588323
        patchset: 01fd7abb7e01e8cc2214be6ba57343b95f588323
        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: 349a0df9232b4eddac3b4ba864d60b00
      buildset_refs:
      - branch: main
        change: '348'
        change_message: 'fix(kubernetes): guard resize without pod QoS cgroups


          ## ENG-219: guard in-place resize without pod QoS cgroups


          ### Problem


          Older collection releases joined kubelets with:


          ```text

          --cgroups-per-qos=false --enforce-node-allocatable=

          ```


          Kubeadm preserves those arguments in `/var/lib/kubelet/kubeadm-flags.env`
          across upgrades. A cluster can therefore reach Kubernetes 1.35 or later
          while some kubelets still run without pod QoS cgroups.


          Kubernetes 1.35 made in-place pod resize generally available. On an affected
          node, a resize can reach a nil pod-cgroup configuration and crash the kubelet,
          as described in [kubernetes/kubernetes#137993](https://github.com/kubernetes/kubernetes/issues/137993).
          The upstream correction is tracked by [kubernetes/kubernetes#137999](https://github.com/kubernetes/kubernetes/pull/137999).


          There are two trigger paths:


          1. **API-initiated resize:** an API client updates `pods/resize`; admission
          can block this path.

          2. **Kubelet-initiated reconciliation:** releases containing the behavior
          from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387)
          can reach the vulnerable path internally; admission cannot intercept it.


          ### Safety model


          This change adds two protections:


          - A hard per-minor version denylist for releases where kubelet-initiated
          reconciliation can trigger the panic.

          - A `ValidatingAdmissionPolicy` and binding for affected releases where
          API-initiated resize remains the trigger.


          The policy:


          - matches only `UPDATE` requests to the core `v1` `pods/resize` subresource;

          - leaves ordinary Pod updates unaffected;

          - uses `failurePolicy: Fail`;

          - creates the policy before its binding;

          - deletes the binding before the policy;

          - remains installed while any affected kubelet lacks pod QoS cgroups or
          safety evidence is incomplete.


          On a new cluster, the guard is applied immediately after the first API server
          becomes available and before additional control-plane or worker nodes join.
          On an existing cluster, it is applied before joins and before any kubelet
          upgrade to 1.35+.


          Creating the policy objects is not treated as proof of enforcement. After
          creating the policy and binding, the role generates a unique probe name
          on the Ansible controller before submitting the Pod create request. The
          name therefore remains available to the `always` cleanup even if the API
          server commits the create but the client loses the response. EndpointSlice
          discovery retries until it finds a ready endpoint with an address and a
          non-null HTTPS port. The role then waits until every discovered ready API
          server can read the probe and sends a server-side dry-run `pods/resize`
          request directly to every server. Success requires a nonzero response containing
          both `ValidatingAdmissionPolicy ''<managed-name>''` and the exact managed
          validation message. Generic Pod errors and denials from another policy remain
          failures, and retry exhaustion stops the play. Cleanup targets only the
          pre-generated name from this invocation before joins or upgrades can continue.


          ### Cluster-wide inspection


          The preflight uses the Kubernetes API as the primary source of effective
          state:


          - `status.nodeInfo.kubeletVersion` provides the running kubelet version.

          - `/api/v1/nodes/<name>/proxy/configz` provides effective `cgroupsPerQOS`,
          including command-line overrides.

          - Every Node returned by the API is inspected, including Nodes no longer
          represented in Ansible inventory.


          An explicitly configured `kubernetes_bootstrap_node` is tried first, followed
          by every control-plane host. Transport failures and delegate-wide `api_error`
          results fall through to the next controller. Results with node-local `configz`
          errors are retained as a conservative fallback while later controllers are
          tried for complete evidence.


          For a play host with no Node object, local kubelet flags and configuration
          are inspected. Failed reads remain unknown; only a successfully confirmed
          absent file permits inventory/default evidence.


          API inspection, untracked-Node classification, and the final safety decision
          are calculated once on a designated fact host. The resulting facts are then
          explicitly published to every active play host before the Kubernetes role
          continues. A denylisted target fails cluster-wide with `any_errors_fatal`.


          If no controller can enumerate Nodes, local host inspection is insufficient
          to prove that no out-of-inventory Nodes exist. The role therefore records
          a cluster-level unknown, retains the admission guard, and rejects denylisted
          targets. File absence is not accepted as cluster-history evidence because
          reset or replacement hosts can lack kubelet state while an older out-of-inventory
          Node remains active.


          The API-enumeration exception is available only when an operator explicitly
          sets `kubernetes_upgrade_check_assert_fresh_bootstrap: true` for the first
          bootstrap of a cluster. It defaults to false and is honored only when the
          complete Kubernetes inventory is present in the play, every play host can
          be checked, and every host lacks `/etc/kubernetes/kubelet.conf`. An existing
          marker, failed read, or unreachable host rejects a stale assertion. The
          assertion is documented as a one-run `--extra-vars` value and must not be
          persisted in inventory or used for recovery, reset, replacement, or rejoin
          operations. Failed API enumeration in a limited play does not open Ansible
          connections to hosts outside that play.


          ### Policy lifecycle


          The collection manages:


          ```text

          ValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard

          ValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard

          ```


          The guard is required when:


          - the target version is in an affected resize range and any inventory or
          API-only Node lacks pod QoS cgroups;

          - an installed kubelet on a legacy node remains in an affected range;

          - a Node has unknown QoS-cgroup or installed-version state; or

          - complete API Node enumeration cannot be established on an existing cluster.


          It is removed only when complete evidence shows that no affected kubelet
          remains vulnerable. Per-minor ranges allow each Kubernetes branch to be
          opened independently when the upstream fix is released.


          ### Migration workflow


          `docs/ops/qos-cgroups.md` documents the permanent remediation:


          - migrate one node at a time, workers before control-plane nodes;

          - preserve workload and stacked-etcd quorum;

          - drain, reset, delete the old Node object, and rejoin instead of editing
          kubelet flags in place;

          - register the replacement with a temporary `NoSchedule` taint so it is
          protected from its first API registration;

          - keep the taint through kubelet, `configz`, runtime-driver, workload, and
          control-plane health validation;

          - remove the taint only after every applicable check passes;

          - keep the migration separate from the Kubernetes version upgrade.


          The runbook also refreshes the shared kubelet ConfigMap before rejoin and
          verifies kubelet/containerd cgroup-driver agreement.


          ### CI coverage


          Two voting Zuul scenarios run in both check and gate:


          - `cluster-upgrade-resize-guard` performs a `1.34.9 -> 1.35.6` upgrade from
          legacy QoS-cgroup-disabled nodes and runs the enforcement barrier before
          the upgrade. It verifies policy enforcement, probe cleanup, ordinary Pod
          updates, denied resize behavior, kubelet health, and upgrade canaries.

          - `cluster-upgrade-resize-cleanup` seeds stale policy and binding resources
          on a QoS-enabled cluster and verifies their actual removal. It skips only
          the unrelated Cilium restart assertion that keeps the generic upgrade job
          non-voting.


          ### Validation


          - `231` unit tests pass.

          - Full pre-commit, Black, Flake8, isort, YAML lint, and Ansible lint pass.

          - `ansible-test sanity --test validate-modules plugins/modules/kubelet_configz.py`
          passes. The new module uses the required GPLv3 header, and the module and
          new `version_matching_ranges` filter declare `version_added: 3.6.0`.

          - `git diff --check` passes.

          - A read-only multi-host rehearsal forced the preferred API delegate to
          be unreachable, retried a healthy controller, enumerated all Nodes, and
          verified identical safety facts on every play host.

          - A second read-only multi-host rehearsal forced every selected delegate
          to return no usable API enumeration and verified every play host retained
          the guard through the same cluster-level unknown result. Regression coverage
          additionally verifies that freshness requires an explicit full-inventory
          assertion and that failed API enumeration performs no inventory-wide marker
          probe.

          - Both rehearsals completed with `changed=0`, `unreachable=0`, and `failed=0`.

          - A live Kubernetes `1.36.2` rehearsal verified controller-side probe-name
          generation, ready-HTTPS EndpointSlice discovery, and the exact managed-policy
          signature and validation message directly through all three API servers.
          The generated probe was visible through every endpoint, was removed by its
          pre-generated name, and the existing-guard run completed with `changed=0`,
          `unreachable=0`, and `failed=0`.

          - Failure-path rehearsals proved that Pod `NotFound`, an invalid assigned
          Node, and denials from a different policy exhaust retries and end with `failed=1`.
          In the new-policy propagation rehearsal, one API server observed the temporary
          policy while two still returned the pre-existing policy; the barrier correctly
          refused to continue and the `always` cleanup removed the generated probe
          and temporary policy resources.

          - The pre-existing guard remained installed, no generated probe Pods remained,
          and every node remained `Ready` after the rehearsals.

          '
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/348
        commit_id: 01fd7abb7e01e8cc2214be6ba57343b95f588323
        patchset: 01fd7abb7e01e8cc2214be6ba57343b95f588323
        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: '348'
      change_message: 'fix(kubernetes): guard resize without pod QoS cgroups


        ## ENG-219: guard in-place resize without pod QoS cgroups


        ### Problem


        Older collection releases joined kubelets with:


        ```text

        --cgroups-per-qos=false --enforce-node-allocatable=

        ```


        Kubeadm preserves those arguments in `/var/lib/kubelet/kubeadm-flags.env`
        across upgrades. A cluster can therefore reach Kubernetes 1.35 or later while
        some kubelets still run without pod QoS cgroups.


        Kubernetes 1.35 made in-place pod resize generally available. On an affected
        node, a resize can reach a nil pod-cgroup configuration and crash the kubelet,
        as described in [kubernetes/kubernetes#137993](https://github.com/kubernetes/kubernetes/issues/137993).
        The upstream correction is tracked by [kubernetes/kubernetes#137999](https://github.com/kubernetes/kubernetes/pull/137999).


        There are two trigger paths:


        1. **API-initiated resize:** an API client updates `pods/resize`; admission
        can block this path.

        2. **Kubelet-initiated reconciliation:** releases containing the behavior
        from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387)
        can reach the vulnerable path internally; admission cannot intercept it.


        ### Safety model


        This change adds two protections:


        - A hard per-minor version denylist for releases where kubelet-initiated reconciliation
        can trigger the panic.

        - A `ValidatingAdmissionPolicy` and binding for affected releases where API-initiated
        resize remains the trigger.


        The policy:


        - matches only `UPDATE` requests to the core `v1` `pods/resize` subresource;

        - leaves ordinary Pod updates unaffected;

        - uses `failurePolicy: Fail`;

        - creates the policy before its binding;

        - deletes the binding before the policy;

        - remains installed while any affected kubelet lacks pod QoS cgroups or safety
        evidence is incomplete.


        On a new cluster, the guard is applied immediately after the first API server
        becomes available and before additional control-plane or worker nodes join.
        On an existing cluster, it is applied before joins and before any kubelet
        upgrade to 1.35+.


        Creating the policy objects is not treated as proof of enforcement. After
        creating the policy and binding, the role generates a unique probe name on
        the Ansible controller before submitting the Pod create request. The name
        therefore remains available to the `always` cleanup even if the API server
        commits the create but the client loses the response. EndpointSlice discovery
        retries until it finds a ready endpoint with an address and a non-null HTTPS
        port. The role then waits until every discovered ready API server can read
        the probe and sends a server-side dry-run `pods/resize` request directly to
        every server. Success requires a nonzero response containing both `ValidatingAdmissionPolicy
        ''<managed-name>''` and the exact managed validation message. Generic Pod
        errors and denials from another policy remain failures, and retry exhaustion
        stops the play. Cleanup targets only the pre-generated name from this invocation
        before joins or upgrades can continue.


        ### Cluster-wide inspection


        The preflight uses the Kubernetes API as the primary source of effective state:


        - `status.nodeInfo.kubeletVersion` provides the running kubelet version.

        - `/api/v1/nodes/<name>/proxy/configz` provides effective `cgroupsPerQOS`,
        including command-line overrides.

        - Every Node returned by the API is inspected, including Nodes no longer represented
        in Ansible inventory.


        An explicitly configured `kubernetes_bootstrap_node` is tried first, followed
        by every control-plane host. Transport failures and delegate-wide `api_error`
        results fall through to the next controller. Results with node-local `configz`
        errors are retained as a conservative fallback while later controllers are
        tried for complete evidence.


        For a play host with no Node object, local kubelet flags and configuration
        are inspected. Failed reads remain unknown; only a successfully confirmed
        absent file permits inventory/default evidence.


        API inspection, untracked-Node classification, and the final safety decision
        are calculated once on a designated fact host. The resulting facts are then
        explicitly published to every active play host before the Kubernetes role
        continues. A denylisted target fails cluster-wide with `any_errors_fatal`.


        If no controller can enumerate Nodes, local host inspection is insufficient
        to prove that no out-of-inventory Nodes exist. The role therefore records
        a cluster-level unknown, retains the admission guard, and rejects denylisted
        targets. File absence is not accepted as cluster-history evidence because
        reset or replacement hosts can lack kubelet state while an older out-of-inventory
        Node remains active.


        The API-enumeration exception is available only when an operator explicitly
        sets `kubernetes_upgrade_check_assert_fresh_bootstrap: true` for the first
        bootstrap of a cluster. It defaults to false and is honored only when the
        complete Kubernetes inventory is present in the play, every play host can
        be checked, and every host lacks `/etc/kubernetes/kubelet.conf`. An existing
        marker, failed read, or unreachable host rejects a stale assertion. The assertion
        is documented as a one-run `--extra-vars` value and must not be persisted
        in inventory or used for recovery, reset, replacement, or rejoin operations.
        Failed API enumeration in a limited play does not open Ansible connections
        to hosts outside that play.


        ### Policy lifecycle


        The collection manages:


        ```text

        ValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard

        ValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard

        ```


        The guard is required when:


        - the target version is in an affected resize range and any inventory or API-only
        Node lacks pod QoS cgroups;

        - an installed kubelet on a legacy node remains in an affected range;

        - a Node has unknown QoS-cgroup or installed-version state; or

        - complete API Node enumeration cannot be established on an existing cluster.


        It is removed only when complete evidence shows that no affected kubelet remains
        vulnerable. Per-minor ranges allow each Kubernetes branch to be opened independently
        when the upstream fix is released.


        ### Migration workflow


        `docs/ops/qos-cgroups.md` documents the permanent remediation:


        - migrate one node at a time, workers before control-plane nodes;

        - preserve workload and stacked-etcd quorum;

        - drain, reset, delete the old Node object, and rejoin instead of editing
        kubelet flags in place;

        - register the replacement with a temporary `NoSchedule` taint so it is protected
        from its first API registration;

        - keep the taint through kubelet, `configz`, runtime-driver, workload, and
        control-plane health validation;

        - remove the taint only after every applicable check passes;

        - keep the migration separate from the Kubernetes version upgrade.


        The runbook also refreshes the shared kubelet ConfigMap before rejoin and
        verifies kubelet/containerd cgroup-driver agreement.


        ### CI coverage


        Two voting Zuul scenarios run in both check and gate:


        - `cluster-upgrade-resize-guard` performs a `1.34.9 -> 1.35.6` upgrade from
        legacy QoS-cgroup-disabled nodes and runs the enforcement barrier before the
        upgrade. It verifies policy enforcement, probe cleanup, ordinary Pod updates,
        denied resize behavior, kubelet health, and upgrade canaries.

        - `cluster-upgrade-resize-cleanup` seeds stale policy and binding resources
        on a QoS-enabled cluster and verifies their actual removal. It skips only
        the unrelated Cilium restart assertion that keeps the generic upgrade job
        non-voting.


        ### Validation


        - `231` unit tests pass.

        - Full pre-commit, Black, Flake8, isort, YAML lint, and Ansible lint pass.

        - `ansible-test sanity --test validate-modules plugins/modules/kubelet_configz.py`
        passes. The new module uses the required GPLv3 header, and the module and
        new `version_matching_ranges` filter declare `version_added: 3.6.0`.

        - `git diff --check` passes.

        - A read-only multi-host rehearsal forced the preferred API delegate to be
        unreachable, retried a healthy controller, enumerated all Nodes, and verified
        identical safety facts on every play host.

        - A second read-only multi-host rehearsal forced every selected delegate to
        return no usable API enumeration and verified every play host retained the
        guard through the same cluster-level unknown result. Regression coverage additionally
        verifies that freshness requires an explicit full-inventory assertion and
        that failed API enumeration performs no inventory-wide marker probe.

        - Both rehearsals completed with `changed=0`, `unreachable=0`, and `failed=0`.

        - A live Kubernetes `1.36.2` rehearsal verified controller-side probe-name
        generation, ready-HTTPS EndpointSlice discovery, and the exact managed-policy
        signature and validation message directly through all three API servers. The
        generated probe was visible through every endpoint, was removed by its pre-generated
        name, and the existing-guard run completed with `changed=0`, `unreachable=0`,
        and `failed=0`.

        - Failure-path rehearsals proved that Pod `NotFound`, an invalid assigned
        Node, and denials from a different policy exhaust retries and end with `failed=1`.
        In the new-policy propagation rehearsal, one API server observed the temporary
        policy while two still returned the pre-existing policy; the barrier correctly
        refused to continue and the `always` cleanup removed the generated probe and
        temporary policy resources.

        - The pre-existing guard remained installed, no generated probe Pods remained,
        and every node remained `Ready` after the rehearsals.

        '
      change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/348
      child_jobs: []
      commit_id: 01fd7abb7e01e8cc2214be6ba57343b95f588323
      event_id: 680d5f30-da7d-11f1-9efe-02b6465560c2
      executor:
        hostname: 2d72f0692154
        inventory_file: /var/lib/zuul/builds/fc433883fbfc40d697c9eaacf906451c/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/fc433883fbfc40d697c9eaacf906451c/work/logs
        result_data_file: /var/lib/zuul/builds/fc433883fbfc40d697c9eaacf906451c/work/results.json
        src_root: /var/lib/zuul/builds/fc433883fbfc40d697c9eaacf906451c/work/src
        work_root: /var/lib/zuul/builds/fc433883fbfc40d697c9eaacf906451c/work
      include_vars: []
      items:
      - branch: main
        change: '348'
        change_message: 'fix(kubernetes): guard resize without pod QoS cgroups


          ## ENG-219: guard in-place resize without pod QoS cgroups


          ### Problem


          Older collection releases joined kubelets with:


          ```text

          --cgroups-per-qos=false --enforce-node-allocatable=

          ```


          Kubeadm preserves those arguments in `/var/lib/kubelet/kubeadm-flags.env`
          across upgrades. A cluster can therefore reach Kubernetes 1.35 or later
          while some kubelets still run without pod QoS cgroups.


          Kubernetes 1.35 made in-place pod resize generally available. On an affected
          node, a resize can reach a nil pod-cgroup configuration and crash the kubelet,
          as described in [kubernetes/kubernetes#137993](https://github.com/kubernetes/kubernetes/issues/137993).
          The upstream correction is tracked by [kubernetes/kubernetes#137999](https://github.com/kubernetes/kubernetes/pull/137999).


          There are two trigger paths:


          1. **API-initiated resize:** an API client updates `pods/resize`; admission
          can block this path.

          2. **Kubelet-initiated reconciliation:** releases containing the behavior
          from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387)
          can reach the vulnerable path internally; admission cannot intercept it.


          ### Safety model


          This change adds two protections:


          - A hard per-minor version denylist for releases where kubelet-initiated
          reconciliation can trigger the panic.

          - A `ValidatingAdmissionPolicy` and binding for affected releases where
          API-initiated resize remains the trigger.


          The policy:


          - matches only `UPDATE` requests to the core `v1` `pods/resize` subresource;

          - leaves ordinary Pod updates unaffected;

          - uses `failurePolicy: Fail`;

          - creates the policy before its binding;

          - deletes the binding before the policy;

          - remains installed while any affected kubelet lacks pod QoS cgroups or
          safety evidence is incomplete.


          On a new cluster, the guard is applied immediately after the first API server
          becomes available and before additional control-plane or worker nodes join.
          On an existing cluster, it is applied before joins and before any kubelet
          upgrade to 1.35+.


          Creating the policy objects is not treated as proof of enforcement. After
          creating the policy and binding, the role generates a unique probe name
          on the Ansible controller before submitting the Pod create request. The
          name therefore remains available to the `always` cleanup even if the API
          server commits the create but the client loses the response. EndpointSlice
          discovery retries until it finds a ready endpoint with an address and a
          non-null HTTPS port. The role then waits until every discovered ready API
          server can read the probe and sends a server-side dry-run `pods/resize`
          request directly to every server. Success requires a nonzero response containing
          both `ValidatingAdmissionPolicy ''<managed-name>''` and the exact managed
          validation message. Generic Pod errors and denials from another policy remain
          failures, and retry exhaustion stops the play. Cleanup targets only the
          pre-generated name from this invocation before joins or upgrades can continue.


          ### Cluster-wide inspection


          The preflight uses the Kubernetes API as the primary source of effective
          state:


          - `status.nodeInfo.kubeletVersion` provides the running kubelet version.

          - `/api/v1/nodes/<name>/proxy/configz` provides effective `cgroupsPerQOS`,
          including command-line overrides.

          - Every Node returned by the API is inspected, including Nodes no longer
          represented in Ansible inventory.


          An explicitly configured `kubernetes_bootstrap_node` is tried first, followed
          by every control-plane host. Transport failures and delegate-wide `api_error`
          results fall through to the next controller. Results with node-local `configz`
          errors are retained as a conservative fallback while later controllers are
          tried for complete evidence.


          For a play host with no Node object, local kubelet flags and configuration
          are inspected. Failed reads remain unknown; only a successfully confirmed
          absent file permits inventory/default evidence.


          API inspection, untracked-Node classification, and the final safety decision
          are calculated once on a designated fact host. The resulting facts are then
          explicitly published to every active play host before the Kubernetes role
          continues. A denylisted target fails cluster-wide with `any_errors_fatal`.


          If no controller can enumerate Nodes, local host inspection is insufficient
          to prove that no out-of-inventory Nodes exist. The role therefore records
          a cluster-level unknown, retains the admission guard, and rejects denylisted
          targets. File absence is not accepted as cluster-history evidence because
          reset or replacement hosts can lack kubelet state while an older out-of-inventory
          Node remains active.


          The API-enumeration exception is available only when an operator explicitly
          sets `kubernetes_upgrade_check_assert_fresh_bootstrap: true` for the first
          bootstrap of a cluster. It defaults to false and is honored only when the
          complete Kubernetes inventory is present in the play, every play host can
          be checked, and every host lacks `/etc/kubernetes/kubelet.conf`. An existing
          marker, failed read, or unreachable host rejects a stale assertion. The
          assertion is documented as a one-run `--extra-vars` value and must not be
          persisted in inventory or used for recovery, reset, replacement, or rejoin
          operations. Failed API enumeration in a limited play does not open Ansible
          connections to hosts outside that play.


          ### Policy lifecycle


          The collection manages:


          ```text

          ValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard

          ValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard

          ```


          The guard is required when:


          - the target version is in an affected resize range and any inventory or
          API-only Node lacks pod QoS cgroups;

          - an installed kubelet on a legacy node remains in an affected range;

          - a Node has unknown QoS-cgroup or installed-version state; or

          - complete API Node enumeration cannot be established on an existing cluster.


          It is removed only when complete evidence shows that no affected kubelet
          remains vulnerable. Per-minor ranges allow each Kubernetes branch to be
          opened independently when the upstream fix is released.


          ### Migration workflow


          `docs/ops/qos-cgroups.md` documents the permanent remediation:


          - migrate one node at a time, workers before control-plane nodes;

          - preserve workload and stacked-etcd quorum;

          - drain, reset, delete the old Node object, and rejoin instead of editing
          kubelet flags in place;

          - register the replacement with a temporary `NoSchedule` taint so it is
          protected from its first API registration;

          - keep the taint through kubelet, `configz`, runtime-driver, workload, and
          control-plane health validation;

          - remove the taint only after every applicable check passes;

          - keep the migration separate from the Kubernetes version upgrade.


          The runbook also refreshes the shared kubelet ConfigMap before rejoin and
          verifies kubelet/containerd cgroup-driver agreement.


          ### CI coverage


          Two voting Zuul scenarios run in both check and gate:


          - `cluster-upgrade-resize-guard` performs a `1.34.9 -> 1.35.6` upgrade from
          legacy QoS-cgroup-disabled nodes and runs the enforcement barrier before
          the upgrade. It verifies policy enforcement, probe cleanup, ordinary Pod
          updates, denied resize behavior, kubelet health, and upgrade canaries.

          - `cluster-upgrade-resize-cleanup` seeds stale policy and binding resources
          on a QoS-enabled cluster and verifies their actual removal. It skips only
          the unrelated Cilium restart assertion that keeps the generic upgrade job
          non-voting.


          ### Validation


          - `231` unit tests pass.

          - Full pre-commit, Black, Flake8, isort, YAML lint, and Ansible lint pass.

          - `ansible-test sanity --test validate-modules plugins/modules/kubelet_configz.py`
          passes. The new module uses the required GPLv3 header, and the module and
          new `version_matching_ranges` filter declare `version_added: 3.6.0`.

          - `git diff --check` passes.

          - A read-only multi-host rehearsal forced the preferred API delegate to
          be unreachable, retried a healthy controller, enumerated all Nodes, and
          verified identical safety facts on every play host.

          - A second read-only multi-host rehearsal forced every selected delegate
          to return no usable API enumeration and verified every play host retained
          the guard through the same cluster-level unknown result. Regression coverage
          additionally verifies that freshness requires an explicit full-inventory
          assertion and that failed API enumeration performs no inventory-wide marker
          probe.

          - Both rehearsals completed with `changed=0`, `unreachable=0`, and `failed=0`.

          - A live Kubernetes `1.36.2` rehearsal verified controller-side probe-name
          generation, ready-HTTPS EndpointSlice discovery, and the exact managed-policy
          signature and validation message directly through all three API servers.
          The generated probe was visible through every endpoint, was removed by its
          pre-generated name, and the existing-guard run completed with `changed=0`,
          `unreachable=0`, and `failed=0`.

          - Failure-path rehearsals proved that Pod `NotFound`, an invalid assigned
          Node, and denials from a different policy exhaust retries and end with `failed=1`.
          In the new-policy propagation rehearsal, one API server observed the temporary
          policy while two still returned the pre-existing policy; the barrier correctly
          refused to continue and the `always` cleanup removed the generated probe
          and temporary policy resources.

          - The pre-existing guard remained installed, no generated probe Pods remained,
          and every node remained `Ready` after the rehearsals.

          '
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/348
        commit_id: 01fd7abb7e01e8cc2214be6ba57343b95f588323
        patchset: 01fd7abb7e01e8cc2214be6ba57343b95f588323
        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-cluster-api
      jobtags: []
      max_attempts: 3
      message: fix(kubernetes): guard resize without pod QoS cgroups

## ENG-219: guard in-place resize without pod QoS cgroups

### Problem

Older collection releases joined kubelets with:

```text
--cgroups-per-qos=false --enforce-node-allocatable=
```

Kubeadm preserves those arguments in `/var/lib/kubelet/kubeadm-flags.env` across upgrades. A cluster can therefore reach Kubernetes 1.35 or later while some kubelets still run without pod QoS cgroups.

Kubernetes 1.35 made in-place pod resize generally available. On an affected node, a resize can reach a nil pod-cgroup configuration and crash the kubelet, as described in [kubernetes/kubernetes#137993](https://github.com/kubernetes/kubernetes/issues/137993). The upstream correction is tracked by [kubernetes/kubernetes#137999](https://github.com/kubernetes/kubernetes/pull/137999).

There are two trigger paths:

1. **API-initiated resize:** an API client updates `pods/resize`; admission can block this path.
2. **Kubelet-initiated reconciliation:** releases containing the behavior from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387) can reach the vulnerable path internally; admission cannot intercept it.

### Safety model

This change adds two protections:

- A hard per-minor version denylist for releases where kubelet-initiated reconciliation can trigger the panic.
- A `ValidatingAdmissionPolicy` and binding for affected releases where API-initiated resize remains the trigger.

The policy:

- matches only `UPDATE` requests to the core `v1` `pods/resize` subresource;
- leaves ordinary Pod updates unaffected;
- uses `failurePolicy: Fail`;
- creates the policy before its binding;
- deletes the binding before the policy;
- remains installed while any affected kubelet lacks pod QoS cgroups or safety evidence is incomplete.

On a new cluster, the guard is applied immediately after the first API server becomes available and before additional control-plane or worker nodes join. On an existing cluster, it is applied before joins and before any kubelet upgrade to 1.35+.

Creating the policy objects is not treated as proof of enforcement. After creating the policy and binding, the role generates a unique probe name on the Ansible controller before submitting the Pod create request. The name therefore remains available to the `always` cleanup even if the API server commits the create but the client loses the response. EndpointSlice discovery retries until it finds a ready endpoint with an address and a non-null HTTPS port. The role then waits until every discovered ready API server can read the probe and sends a server-side dry-run `pods/resize` request directly to every server. Success requires a nonzero response containing both `ValidatingAdmissionPolicy '<managed-name>'` and the exact managed validation message. Generic Pod errors and denials from another policy remain failures, and retry exhaustion stops the play. Cleanup targets only the pre-generated name from this invocation before joins or upgrades can continue.

### Cluster-wide inspection

The preflight uses the Kubernetes API as the primary source of effective state:

- `status.nodeInfo.kubeletVersion` provides the running kubelet version.
- `/api/v1/nodes/<name>/proxy/configz` provides effective `cgroupsPerQOS`, including command-line overrides.
- Every Node returned by the API is inspected, including Nodes no longer represented in Ansible inventory.

An explicitly configured `kubernetes_bootstrap_node` is tried first, followed by every control-plane host. Transport failures and delegate-wide `api_error` results fall through to the next controller. Results with node-local `configz` errors are retained as a conservative fallback while later controllers are tried for complete evidence.

For a play host with no Node object, local kubelet flags and configuration are inspected. Failed reads remain unknown; only a successfully confirmed absent file permits inventory/default evidence.

API inspection, untracked-Node classification, and the final safety decision are calculated once on a designated fact host. The resulting facts are then explicitly published to every active play host before the Kubernetes role continues. A denylisted target fails cluster-wide with `any_errors_fatal`.

If no controller can enumerate Nodes, local host inspection is insufficient to prove that no out-of-inventory Nodes exist. The role therefore records a cluster-level unknown, retains the admission guard, and rejects denylisted targets. File absence is not accepted as cluster-history evidence because reset or replacement hosts can lack kubelet state while an older out-of-inventory Node remains active.

The API-enumeration exception is available only when an operator explicitly sets `kubernetes_upgrade_check_assert_fresh_bootstrap: true` for the first bootstrap of a cluster. It defaults to false and is honored only when the complete Kubernetes inventory is present in the play, every play host can be checked, and every host lacks `/etc/kubernetes/kubelet.conf`. An existing marker, failed read, or unreachable host rejects a stale assertion. The assertion is documented as a one-run `--extra-vars` value and must not be persisted in inventory or used for recovery, reset, replacement, or rejoin operations. Failed API enumeration in a limited play does not open Ansible connections to hosts outside that play.

### Policy lifecycle

The collection manages:

```text
ValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard
ValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard
```

The guard is required when:

- the target version is in an affected resize range and any inventory or API-only Node lacks pod QoS cgroups;
- an installed kubelet on a legacy node remains in an affected range;
- a Node has unknown QoS-cgroup or installed-version state; or
- complete API Node enumeration cannot be established on an existing cluster.

It is removed only when complete evidence shows that no affected kubelet remains vulnerable. Per-minor ranges allow each Kubernetes branch to be opened independently when the upstream fix is released.

### Migration workflow

`docs/ops/qos-cgroups.md` documents the permanent remediation:

- migrate one node at a time, workers before control-plane nodes;
- preserve workload and stacked-etcd quorum;
- drain, reset, delete the old Node object, and rejoin instead of editing kubelet flags in place;
- register the replacement with a temporary `NoSchedule` taint so it is protected from its first API registration;
- keep the taint through kubelet, `configz`, runtime-driver, workload, and control-plane health validation;
- remove the taint only after every applicable check passes;
- keep the migration separate from the Kubernetes version upgrade.

The runbook also refreshes the shared kubelet ConfigMap before rejoin and verifies kubelet/containerd cgroup-driver agreement.

### CI coverage

Two voting Zuul scenarios run in both check and gate:

- `cluster-upgrade-resize-guard` performs a `1.34.9 -> 1.35.6` upgrade from legacy QoS-cgroup-disabled nodes and runs the enforcement barrier before the upgrade. It verifies policy enforcement, probe cleanup, ordinary Pod updates, denied resize behavior, kubelet health, and upgrade canaries.
- `cluster-upgrade-resize-cleanup` seeds stale policy and binding resources on a QoS-enabled cluster and verifies their actual removal. It skips only the unrelated Cilium restart assertion that keeps the generic upgrade job non-voting.

### Validation

- `231` unit tests pass.
- Full pre-commit, Black, Flake8, isort, YAML lint, and Ansible lint pass.
- `ansible-test sanity --test validate-modules plugins/modules/kubelet_configz.py` passes. The new module uses the required GPLv3 header, and the module and new `version_matching_ranges` filter declare `version_added: 3.6.0`.
- `git diff --check` passes.
- A read-only multi-host rehearsal forced the preferred API delegate to be unreachable, retried a healthy controller, enumerated all Nodes, and verified identical safety facts on every play host.
- A second read-only multi-host rehearsal forced every selected delegate to return no usable API enumeration and verified every play host retained the guard through the same cluster-level unknown result. Regression coverage additionally verifies that freshness requires an explicit full-inventory assertion and that failed API enumeration performs no inventory-wide marker probe.
- Both rehearsals completed with `changed=0`, `unreachable=0`, and `failed=0`.
- A live Kubernetes `1.36.2` rehearsal verified controller-side probe-name generation, ready-HTTPS EndpointSlice discovery, and the exact managed-policy signature and validation message directly through all three API servers. The generated probe was visible through every endpoint, was removed by its pre-generated name, and the existing-guard run completed with `changed=0`, `unreachable=0`, and `failed=0`.
- Failure-path rehearsals proved that Pod `NotFound`, an invalid assigned Node, and denials from a different policy exhaust retries and end with `failed=1`. In the new-policy propagation rehearsal, one API server observed the temporary policy while two still returned the pre-existing policy; the barrier correctly refused to continue and the `always` cleanup removed the generated probe and temporary policy resources.
- The pre-existing guard remained installed, no generated probe Pods remained, and every node remained `Ready` after the rehearsals.

      patchset: 01fd7abb7e01e8cc2214be6ba57343b95f588323
      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: 92e32d78537ff09e7fa1a494a7c4601893e0b382
          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: 92e32d78537ff09e7fa1a494a7c4601893e0b382
          untrusted/project_3/github.com/vexxhost/ansible-collection-kubernetes:
            canonical_name: github.com/vexxhost/ansible-collection-kubernetes
            checkout: main
            commit: be05025df38cf56f851ad5c004ade638c9faa08c
          untrusted/project_4/opendev.org/openstack/openstack-helm:
            canonical_name: opendev.org/openstack/openstack-helm
            checkout: master
            commit: caf54dc50156c71634a88c99ebd3900785a39950
        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: 00d193fd380122715b57c90b3cf03648782feb90
          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: b405909e51bb5d28fce99a075e420ed17c51b83d
          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: be05025df38cf56f851ad5c004ade638c9faa08c
          name: vexxhost/ansible-collection-kubernetes
          required: false
          short_name: ansible-collection-kubernetes
          src_dir: src/github.com/vexxhost/ansible-collection-kubernetes
      ref: refs/pull/348/head
      resources: {}
      tenant: oss
      timeout: 1800
      topic: null
      voting: true
