all:
  children:
    controllers:
      hosts:
        controller: null
    zuul_unreachable:
      hosts: {}
  hosts:
    controller:
      ansible_connection: ssh
      ansible_host: 162.253.55.136
      ansible_port: 22
      ansible_python_interpreter: auto
      ansible_user: zuul
      cilium_helm_values:
        operator:
          replicas: 1
      cilium_ipv4_cidr: 172.24.0.0/16
      kube_vip_address: 172.17.0.100
      kube_vip_bgp_multihop: true
      kube_vip_bgp_peeraddress: '{{ ansible_facts[''default_ipv4''].address }}'
      kube_vip_bgp_routerid: 172.17.0.100
      kube_vip_bgp_sourceip: 172.17.0.100
      kube_vip_interface: '{{ ansible_facts[''default_ipv4''].interface }}'
      kube_vip_mode: bgp
      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: bgp
      nodepool:
        az: yul2
        cloud: public
        external_id: caa07c99-ed36-4e76-85d8-79e7d117d82e
        host_id: 9c7fbe48649bc903922c42a38c50519602ff6769d9b91335dd9e8968
        interface_ip: 162.253.55.136
        label: debian-trixie
        node_properties: {}
        private_ipv4: 162.253.55.136
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.136
        public_ipv6: 2604:e100:1:0:f816:3eff:fe63:1c47
        region: ca-ymq-1
        slot: null
      zuul_node:
        az: yul2
        cloud: public
        external_id: caa07c99-ed36-4e76-85d8-79e7d117d82e
        host_id: 9c7fbe48649bc903922c42a38c50519602ff6769d9b91335dd9e8968
        interface_ip: 162.253.55.136
        label: debian-trixie
        node_properties: {}
        private_ipv4: 162.253.55.136
        private_ipv6: null
        provider: yul1
        public_ipv4: 162.253.55.136
        public_ipv6: 2604:e100:1:0:f816:3eff:fe63:1c47
        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: bgp
    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-bgp explicit: None implied: {MatchAny:{ImpliedBranchMatcher:main}}
        source: vexxhost/ansible-collection-kubernetes/.zuul.yaml@main#115>'
      - '<Job ansible-collection-kubernetes-molecule-bgp explicit: None implied: None
        source: vexxhost/ansible-collection-kubernetes/.zuul.yaml@main#236>'
      ansible_version: '9'
      attempts: 1
      branch: main
      build: 09f69efee5e54792b38d8162e4b4c176
      build_refs:
      - branch: main
        change: '348'
        change_message: "fix(kubernetes): guard resize without pod QoS cgroups\n\n##
          ENG-219: resize admission guard and migration support\n\n### Problem\n\nOlder
          collection releases joined kubelets with:\n\n```text\n--cgroups-per-qos=false
          --enforce-node-allocatable=\n```\n\nKubeadm stores these arguments in `/var/lib/kubelet/kubeadm-flags.env`
          and does not normally rewrite them during an upgrade. A cluster can therefore
          reach Kubernetes 1.35 or later while some kubelets still run without pod
          QoS cgroups.\n\nKubernetes 1.35 made in-place pod resize generally available.
          On an affected node, a `pods/resize` request 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).\n\nThere
          are two distinct trigger paths:\n\n1. **API-initiated resize**\n\n   An
          API client updates `pods/resize`. This path can be blocked through admission.\n\n2.
          **Kubelet-initiated reconciliation**\n\n   Releases containing the behavior
          from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387)
          can reach the same vulnerable path internally. Admission cannot intercept
          this case, so these releases must remain hard-denied until they contain
          the upstream fix.\n\n### Safety model\n\nThis change deliberately keeps
          both protections:\n\n- A hard version denylist for releases where kubelet-initiated
          reconciliation can trigger the panic.\n- A `ValidatingAdmissionPolicy` for
          affected releases where explicit API resize is the remaining trigger.\n\nThe
          admission policy:\n\n- matches only `UPDATE` requests to `pods/resize`;\n-
          leaves ordinary Pod updates unaffected;\n- uses `failurePolicy: Fail`;\n-
          is created before its binding;\n- removes the binding before removing the
          policy;\n- remains installed while any Kubernetes node lacks pod QoS cgroups.\n\nThe
          guard is installed after the control plane reaches the target version and
          before existing kubelets are upgraded. This avoids a window where the API
          accepts resize requests while vulnerable kubelets are running.\n\n### Full-inventory
          detection\n\nThe upgrade preflight now evaluates every host in the configured
          Kubernetes inventory group, even when Ansible is invoked with `--limit`.\n\nFor
          each node it inspects:\n\n- `/var/lib/kubelet/kubeadm-flags.env`;\n- `/etc/default/kubelet`;\n-
          `/var/lib/kubelet/config.yaml`;\n- the installed kubelet version;\n- host-specific
          `kubernetes_kubeadm_extra_args`;\n- host-specific `kubernetes_kubeadm_patches`.\n\nExisting
          kubelet flags take precedence because kubeadm preserves them across upgrades.
          Inventory values are used as a fallback for nodes that have not joined yet.
          An unknown installed kubelet version is treated conservatively as affected.\n\nThe
          play fails if any required node cannot be inspected. It will not remove
          a cluster-wide safety policy based on incomplete evidence from a limited
          play.\n\n### Policy lifecycle\n\nThe collection creates:\n\n```text\nValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard\nValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard\n```\n\nThe
          policy is required when either:\n\n- the target Kubernetes version is in
          an affected resize range and at least one node lacks pod QoS cgroups; or\n-
          an installed kubelet on a legacy node is still in an affected range, including
          during control-plane-only, limited, or interrupted upgrades.\n\nIt is removed
          only after every node uses pod QoS cgroups, or when both the target version
          and every installed kubelet on a remaining legacy node are outside the affected
          ranges. An unknown installed version keeps the policy.\n\nThe affected ranges
          are represented per Kubernetes minor. This allows each branch to be opened
          independently when the upstream fix becomes available in that branch.\n\n###
          CI coverage\n\nA dedicated non-voting Zuul upgrade scenario has been added
          for a `1.34.9 -> 1.35.6` transition.\n\nThe scenario deliberately bootstraps
          the old release with legacy kubelet arguments and then verifies that:\n\n-
          the admission policy and binding are installed;\n- ordinary Pod metadata
          updates continue to work;\n- an explicit `pods/resize` request is rejected
          by the expected policy;\n- the rejected request does not modify the Pod
          resources;\n- the resize probe does not restart a kubelet;\n- the existing
          upgrade canaries remain running.\n\n### Validation completed\n\nLocal validation:\n\n-
          `183` unit tests passed.\n- YAML lint passed for all changed YAML files.\n-
          The Molecule verification playbook passed syntax validation.\n- `git diff
          --check` passed.\n- Check mode was exercised with a limited inventory and
          still inspected the complete Kubernetes node group.\n\nA separate multi-node
          Kubernetes 1.36.2 rehearsal exercised the documented migration against one
          legacy worker:\n\n1. Drain the worker.\n2. Run `kubeadm reset --force`.\n3.
          Delete the stale Node API object.\n4. Reapply the collection with `--limit`
          for that inventory host.\n5. Wait for the replacement Node object to become
          Ready.\n6. Schedule a Burstable workload onto the rebuilt node.\n7. Verify
          its QoS cgroup placement.\n8. Attempt an in-place resize.\n9. Verify the
          admission denial.\n10. Rerun the play in check mode.\n\nObserved results:\n\n-
          The node rejoined successfully.\n- The rebuilt kubelet no longer contained
          either legacy argument.\n- The Burstable workload was placed under the expected
          `/kubepods/burstable/...` hierarchy.\n- The resize request was rejected
          by `vexxhost-kubelet-resize-guard`.\n- The final limited check-mode run
          reported no changes.\n- The cluster remained healthy after the rehearsal.\n-
          The policy remained installed because other intentionally unmigrated legacy
          nodes were still present.\n\n### Operational documentation\n\n`docs/ops/qos-cgroups.md`
          documents the supported permanent remediation:\n\n- migrate workers before
          control-plane nodes;\n- process only one node at a time;\n- preserve application
          and etcd quorum;\n- drain, reset and rejoin rather than editing kubelet
          flags in place;\n- verify kubelet flags, workload readiness and restart
          behavior;\n- remove the guard only after all nodes use pod QoS cgroups;\n-
          recover or roll back a failed migration without proceeding to another node.\n\nThe
          migration is intentionally separate from a Kubernetes version upgrade. Operators
          should first migrate every node on a safe patch release, verify the cluster,
          and only then continue the Kubernetes upgrade."
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/348
        commit_id: e9230d571cd70c3ad348f19c4756339ca0721b55
        patchset: e9230d571cd70c3ad348f19c4756339ca0721b55
        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: 8868e8d2970c462eabf16d90b8383d13
      buildset_refs:
      - branch: main
        change: '348'
        change_message: "fix(kubernetes): guard resize without pod QoS cgroups\n\n##
          ENG-219: resize admission guard and migration support\n\n### Problem\n\nOlder
          collection releases joined kubelets with:\n\n```text\n--cgroups-per-qos=false
          --enforce-node-allocatable=\n```\n\nKubeadm stores these arguments in `/var/lib/kubelet/kubeadm-flags.env`
          and does not normally rewrite them during an upgrade. A cluster can therefore
          reach Kubernetes 1.35 or later while some kubelets still run without pod
          QoS cgroups.\n\nKubernetes 1.35 made in-place pod resize generally available.
          On an affected node, a `pods/resize` request 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).\n\nThere
          are two distinct trigger paths:\n\n1. **API-initiated resize**\n\n   An
          API client updates `pods/resize`. This path can be blocked through admission.\n\n2.
          **Kubelet-initiated reconciliation**\n\n   Releases containing the behavior
          from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387)
          can reach the same vulnerable path internally. Admission cannot intercept
          this case, so these releases must remain hard-denied until they contain
          the upstream fix.\n\n### Safety model\n\nThis change deliberately keeps
          both protections:\n\n- A hard version denylist for releases where kubelet-initiated
          reconciliation can trigger the panic.\n- A `ValidatingAdmissionPolicy` for
          affected releases where explicit API resize is the remaining trigger.\n\nThe
          admission policy:\n\n- matches only `UPDATE` requests to `pods/resize`;\n-
          leaves ordinary Pod updates unaffected;\n- uses `failurePolicy: Fail`;\n-
          is created before its binding;\n- removes the binding before removing the
          policy;\n- remains installed while any Kubernetes node lacks pod QoS cgroups.\n\nThe
          guard is installed after the control plane reaches the target version and
          before existing kubelets are upgraded. This avoids a window where the API
          accepts resize requests while vulnerable kubelets are running.\n\n### Full-inventory
          detection\n\nThe upgrade preflight now evaluates every host in the configured
          Kubernetes inventory group, even when Ansible is invoked with `--limit`.\n\nFor
          each node it inspects:\n\n- `/var/lib/kubelet/kubeadm-flags.env`;\n- `/etc/default/kubelet`;\n-
          `/var/lib/kubelet/config.yaml`;\n- the installed kubelet version;\n- host-specific
          `kubernetes_kubeadm_extra_args`;\n- host-specific `kubernetes_kubeadm_patches`.\n\nExisting
          kubelet flags take precedence because kubeadm preserves them across upgrades.
          Inventory values are used as a fallback for nodes that have not joined yet.
          An unknown installed kubelet version is treated conservatively as affected.\n\nThe
          play fails if any required node cannot be inspected. It will not remove
          a cluster-wide safety policy based on incomplete evidence from a limited
          play.\n\n### Policy lifecycle\n\nThe collection creates:\n\n```text\nValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard\nValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard\n```\n\nThe
          policy is required when either:\n\n- the target Kubernetes version is in
          an affected resize range and at least one node lacks pod QoS cgroups; or\n-
          an installed kubelet on a legacy node is still in an affected range, including
          during control-plane-only, limited, or interrupted upgrades.\n\nIt is removed
          only after every node uses pod QoS cgroups, or when both the target version
          and every installed kubelet on a remaining legacy node are outside the affected
          ranges. An unknown installed version keeps the policy.\n\nThe affected ranges
          are represented per Kubernetes minor. This allows each branch to be opened
          independently when the upstream fix becomes available in that branch.\n\n###
          CI coverage\n\nA dedicated non-voting Zuul upgrade scenario has been added
          for a `1.34.9 -> 1.35.6` transition.\n\nThe scenario deliberately bootstraps
          the old release with legacy kubelet arguments and then verifies that:\n\n-
          the admission policy and binding are installed;\n- ordinary Pod metadata
          updates continue to work;\n- an explicit `pods/resize` request is rejected
          by the expected policy;\n- the rejected request does not modify the Pod
          resources;\n- the resize probe does not restart a kubelet;\n- the existing
          upgrade canaries remain running.\n\n### Validation completed\n\nLocal validation:\n\n-
          `183` unit tests passed.\n- YAML lint passed for all changed YAML files.\n-
          The Molecule verification playbook passed syntax validation.\n- `git diff
          --check` passed.\n- Check mode was exercised with a limited inventory and
          still inspected the complete Kubernetes node group.\n\nA separate multi-node
          Kubernetes 1.36.2 rehearsal exercised the documented migration against one
          legacy worker:\n\n1. Drain the worker.\n2. Run `kubeadm reset --force`.\n3.
          Delete the stale Node API object.\n4. Reapply the collection with `--limit`
          for that inventory host.\n5. Wait for the replacement Node object to become
          Ready.\n6. Schedule a Burstable workload onto the rebuilt node.\n7. Verify
          its QoS cgroup placement.\n8. Attempt an in-place resize.\n9. Verify the
          admission denial.\n10. Rerun the play in check mode.\n\nObserved results:\n\n-
          The node rejoined successfully.\n- The rebuilt kubelet no longer contained
          either legacy argument.\n- The Burstable workload was placed under the expected
          `/kubepods/burstable/...` hierarchy.\n- The resize request was rejected
          by `vexxhost-kubelet-resize-guard`.\n- The final limited check-mode run
          reported no changes.\n- The cluster remained healthy after the rehearsal.\n-
          The policy remained installed because other intentionally unmigrated legacy
          nodes were still present.\n\n### Operational documentation\n\n`docs/ops/qos-cgroups.md`
          documents the supported permanent remediation:\n\n- migrate workers before
          control-plane nodes;\n- process only one node at a time;\n- preserve application
          and etcd quorum;\n- drain, reset and rejoin rather than editing kubelet
          flags in place;\n- verify kubelet flags, workload readiness and restart
          behavior;\n- remove the guard only after all nodes use pod QoS cgroups;\n-
          recover or roll back a failed migration without proceeding to another node.\n\nThe
          migration is intentionally separate from a Kubernetes version upgrade. Operators
          should first migrate every node on a safe patch release, verify the cluster,
          and only then continue the Kubernetes upgrade."
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/348
        commit_id: e9230d571cd70c3ad348f19c4756339ca0721b55
        patchset: e9230d571cd70c3ad348f19c4756339ca0721b55
        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\n\n##
        ENG-219: resize admission guard and migration support\n\n### Problem\n\nOlder
        collection releases joined kubelets with:\n\n```text\n--cgroups-per-qos=false
        --enforce-node-allocatable=\n```\n\nKubeadm stores these arguments in `/var/lib/kubelet/kubeadm-flags.env`
        and does not normally rewrite them during an upgrade. A cluster can therefore
        reach Kubernetes 1.35 or later while some kubelets still run without pod QoS
        cgroups.\n\nKubernetes 1.35 made in-place pod resize generally available.
        On an affected node, a `pods/resize` request 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).\n\nThere
        are two distinct trigger paths:\n\n1. **API-initiated resize**\n\n   An API
        client updates `pods/resize`. This path can be blocked through admission.\n\n2.
        **Kubelet-initiated reconciliation**\n\n   Releases containing the behavior
        from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387)
        can reach the same vulnerable path internally. Admission cannot intercept
        this case, so these releases must remain hard-denied until they contain the
        upstream fix.\n\n### Safety model\n\nThis change deliberately keeps both protections:\n\n-
        A hard version denylist for releases where kubelet-initiated reconciliation
        can trigger the panic.\n- A `ValidatingAdmissionPolicy` for affected releases
        where explicit API resize is the remaining trigger.\n\nThe admission policy:\n\n-
        matches only `UPDATE` requests to `pods/resize`;\n- leaves ordinary Pod updates
        unaffected;\n- uses `failurePolicy: Fail`;\n- is created before its binding;\n-
        removes the binding before removing the policy;\n- remains installed while
        any Kubernetes node lacks pod QoS cgroups.\n\nThe guard is installed after
        the control plane reaches the target version and before existing kubelets
        are upgraded. This avoids a window where the API accepts resize requests while
        vulnerable kubelets are running.\n\n### Full-inventory detection\n\nThe upgrade
        preflight now evaluates every host in the configured Kubernetes inventory
        group, even when Ansible is invoked with `--limit`.\n\nFor each node it inspects:\n\n-
        `/var/lib/kubelet/kubeadm-flags.env`;\n- `/etc/default/kubelet`;\n- `/var/lib/kubelet/config.yaml`;\n-
        the installed kubelet version;\n- host-specific `kubernetes_kubeadm_extra_args`;\n-
        host-specific `kubernetes_kubeadm_patches`.\n\nExisting kubelet flags take
        precedence because kubeadm preserves them across upgrades. Inventory values
        are used as a fallback for nodes that have not joined yet. An unknown installed
        kubelet version is treated conservatively as affected.\n\nThe play fails if
        any required node cannot be inspected. It will not remove a cluster-wide safety
        policy based on incomplete evidence from a limited play.\n\n### Policy lifecycle\n\nThe
        collection creates:\n\n```text\nValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard\nValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard\n```\n\nThe
        policy is required when either:\n\n- the target Kubernetes version is in an
        affected resize range and at least one node lacks pod QoS cgroups; or\n- an
        installed kubelet on a legacy node is still in an affected range, including
        during control-plane-only, limited, or interrupted upgrades.\n\nIt is removed
        only after every node uses pod QoS cgroups, or when both the target version
        and every installed kubelet on a remaining legacy node are outside the affected
        ranges. An unknown installed version keeps the policy.\n\nThe affected ranges
        are represented per Kubernetes minor. This allows each branch to be opened
        independently when the upstream fix becomes available in that branch.\n\n###
        CI coverage\n\nA dedicated non-voting Zuul upgrade scenario has been added
        for a `1.34.9 -> 1.35.6` transition.\n\nThe scenario deliberately bootstraps
        the old release with legacy kubelet arguments and then verifies that:\n\n-
        the admission policy and binding are installed;\n- ordinary Pod metadata updates
        continue to work;\n- an explicit `pods/resize` request is rejected by the
        expected policy;\n- the rejected request does not modify the Pod resources;\n-
        the resize probe does not restart a kubelet;\n- the existing upgrade canaries
        remain running.\n\n### Validation completed\n\nLocal validation:\n\n- `183`
        unit tests passed.\n- YAML lint passed for all changed YAML files.\n- The
        Molecule verification playbook passed syntax validation.\n- `git diff --check`
        passed.\n- Check mode was exercised with a limited inventory and still inspected
        the complete Kubernetes node group.\n\nA separate multi-node Kubernetes 1.36.2
        rehearsal exercised the documented migration against one legacy worker:\n\n1.
        Drain the worker.\n2. Run `kubeadm reset --force`.\n3. Delete the stale Node
        API object.\n4. Reapply the collection with `--limit` for that inventory host.\n5.
        Wait for the replacement Node object to become Ready.\n6. Schedule a Burstable
        workload onto the rebuilt node.\n7. Verify its QoS cgroup placement.\n8. Attempt
        an in-place resize.\n9. Verify the admission denial.\n10. Rerun the play in
        check mode.\n\nObserved results:\n\n- The node rejoined successfully.\n- The
        rebuilt kubelet no longer contained either legacy argument.\n- The Burstable
        workload was placed under the expected `/kubepods/burstable/...` hierarchy.\n-
        The resize request was rejected by `vexxhost-kubelet-resize-guard`.\n- The
        final limited check-mode run reported no changes.\n- The cluster remained
        healthy after the rehearsal.\n- The policy remained installed because other
        intentionally unmigrated legacy nodes were still present.\n\n### Operational
        documentation\n\n`docs/ops/qos-cgroups.md` documents the supported permanent
        remediation:\n\n- migrate workers before control-plane nodes;\n- process only
        one node at a time;\n- preserve application and etcd quorum;\n- drain, reset
        and rejoin rather than editing kubelet flags in place;\n- verify kubelet flags,
        workload readiness and restart behavior;\n- remove the guard only after all
        nodes use pod QoS cgroups;\n- recover or roll back a failed migration without
        proceeding to another node.\n\nThe migration is intentionally separate from
        a Kubernetes version upgrade. Operators should first migrate every node on
        a safe patch release, verify the cluster, and only then continue the Kubernetes
        upgrade."
      change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/348
      child_jobs: []
      commit_id: e9230d571cd70c3ad348f19c4756339ca0721b55
      event_id: a7e509d0-da20-11f1-9372-81b68dfe96aa
      executor:
        hostname: 2d72f0692154
        inventory_file: /var/lib/zuul/builds/09f69efee5e54792b38d8162e4b4c176/ansible/inventory.yaml
        log_root: /var/lib/zuul/builds/09f69efee5e54792b38d8162e4b4c176/work/logs
        result_data_file: /var/lib/zuul/builds/09f69efee5e54792b38d8162e4b4c176/work/results.json
        src_root: /var/lib/zuul/builds/09f69efee5e54792b38d8162e4b4c176/work/src
        work_root: /var/lib/zuul/builds/09f69efee5e54792b38d8162e4b4c176/work
      include_vars: []
      items:
      - branch: main
        change: '348'
        change_message: "fix(kubernetes): guard resize without pod QoS cgroups\n\n##
          ENG-219: resize admission guard and migration support\n\n### Problem\n\nOlder
          collection releases joined kubelets with:\n\n```text\n--cgroups-per-qos=false
          --enforce-node-allocatable=\n```\n\nKubeadm stores these arguments in `/var/lib/kubelet/kubeadm-flags.env`
          and does not normally rewrite them during an upgrade. A cluster can therefore
          reach Kubernetes 1.35 or later while some kubelets still run without pod
          QoS cgroups.\n\nKubernetes 1.35 made in-place pod resize generally available.
          On an affected node, a `pods/resize` request 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).\n\nThere
          are two distinct trigger paths:\n\n1. **API-initiated resize**\n\n   An
          API client updates `pods/resize`. This path can be blocked through admission.\n\n2.
          **Kubelet-initiated reconciliation**\n\n   Releases containing the behavior
          from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387)
          can reach the same vulnerable path internally. Admission cannot intercept
          this case, so these releases must remain hard-denied until they contain
          the upstream fix.\n\n### Safety model\n\nThis change deliberately keeps
          both protections:\n\n- A hard version denylist for releases where kubelet-initiated
          reconciliation can trigger the panic.\n- A `ValidatingAdmissionPolicy` for
          affected releases where explicit API resize is the remaining trigger.\n\nThe
          admission policy:\n\n- matches only `UPDATE` requests to `pods/resize`;\n-
          leaves ordinary Pod updates unaffected;\n- uses `failurePolicy: Fail`;\n-
          is created before its binding;\n- removes the binding before removing the
          policy;\n- remains installed while any Kubernetes node lacks pod QoS cgroups.\n\nThe
          guard is installed after the control plane reaches the target version and
          before existing kubelets are upgraded. This avoids a window where the API
          accepts resize requests while vulnerable kubelets are running.\n\n### Full-inventory
          detection\n\nThe upgrade preflight now evaluates every host in the configured
          Kubernetes inventory group, even when Ansible is invoked with `--limit`.\n\nFor
          each node it inspects:\n\n- `/var/lib/kubelet/kubeadm-flags.env`;\n- `/etc/default/kubelet`;\n-
          `/var/lib/kubelet/config.yaml`;\n- the installed kubelet version;\n- host-specific
          `kubernetes_kubeadm_extra_args`;\n- host-specific `kubernetes_kubeadm_patches`.\n\nExisting
          kubelet flags take precedence because kubeadm preserves them across upgrades.
          Inventory values are used as a fallback for nodes that have not joined yet.
          An unknown installed kubelet version is treated conservatively as affected.\n\nThe
          play fails if any required node cannot be inspected. It will not remove
          a cluster-wide safety policy based on incomplete evidence from a limited
          play.\n\n### Policy lifecycle\n\nThe collection creates:\n\n```text\nValidatingAdmissionPolicy/vexxhost-kubelet-resize-guard\nValidatingAdmissionPolicyBinding/vexxhost-kubelet-resize-guard\n```\n\nThe
          policy is required when either:\n\n- the target Kubernetes version is in
          an affected resize range and at least one node lacks pod QoS cgroups; or\n-
          an installed kubelet on a legacy node is still in an affected range, including
          during control-plane-only, limited, or interrupted upgrades.\n\nIt is removed
          only after every node uses pod QoS cgroups, or when both the target version
          and every installed kubelet on a remaining legacy node are outside the affected
          ranges. An unknown installed version keeps the policy.\n\nThe affected ranges
          are represented per Kubernetes minor. This allows each branch to be opened
          independently when the upstream fix becomes available in that branch.\n\n###
          CI coverage\n\nA dedicated non-voting Zuul upgrade scenario has been added
          for a `1.34.9 -> 1.35.6` transition.\n\nThe scenario deliberately bootstraps
          the old release with legacy kubelet arguments and then verifies that:\n\n-
          the admission policy and binding are installed;\n- ordinary Pod metadata
          updates continue to work;\n- an explicit `pods/resize` request is rejected
          by the expected policy;\n- the rejected request does not modify the Pod
          resources;\n- the resize probe does not restart a kubelet;\n- the existing
          upgrade canaries remain running.\n\n### Validation completed\n\nLocal validation:\n\n-
          `183` unit tests passed.\n- YAML lint passed for all changed YAML files.\n-
          The Molecule verification playbook passed syntax validation.\n- `git diff
          --check` passed.\n- Check mode was exercised with a limited inventory and
          still inspected the complete Kubernetes node group.\n\nA separate multi-node
          Kubernetes 1.36.2 rehearsal exercised the documented migration against one
          legacy worker:\n\n1. Drain the worker.\n2. Run `kubeadm reset --force`.\n3.
          Delete the stale Node API object.\n4. Reapply the collection with `--limit`
          for that inventory host.\n5. Wait for the replacement Node object to become
          Ready.\n6. Schedule a Burstable workload onto the rebuilt node.\n7. Verify
          its QoS cgroup placement.\n8. Attempt an in-place resize.\n9. Verify the
          admission denial.\n10. Rerun the play in check mode.\n\nObserved results:\n\n-
          The node rejoined successfully.\n- The rebuilt kubelet no longer contained
          either legacy argument.\n- The Burstable workload was placed under the expected
          `/kubepods/burstable/...` hierarchy.\n- The resize request was rejected
          by `vexxhost-kubelet-resize-guard`.\n- The final limited check-mode run
          reported no changes.\n- The cluster remained healthy after the rehearsal.\n-
          The policy remained installed because other intentionally unmigrated legacy
          nodes were still present.\n\n### Operational documentation\n\n`docs/ops/qos-cgroups.md`
          documents the supported permanent remediation:\n\n- migrate workers before
          control-plane nodes;\n- process only one node at a time;\n- preserve application
          and etcd quorum;\n- drain, reset and rejoin rather than editing kubelet
          flags in place;\n- verify kubelet flags, workload readiness and restart
          behavior;\n- remove the guard only after all nodes use pod QoS cgroups;\n-
          recover or roll back a failed migration without proceeding to another node.\n\nThe
          migration is intentionally separate from a Kubernetes version upgrade. Operators
          should first migrate every node on a safe patch release, verify the cluster,
          and only then continue the Kubernetes upgrade."
        change_url: https://github.com/vexxhost/ansible-collection-kubernetes/pull/348
        commit_id: e9230d571cd70c3ad348f19c4756339ca0721b55
        patchset: e9230d571cd70c3ad348f19c4756339ca0721b55
        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-bgp
      jobtags: []
      max_attempts: 3
      message: fix(kubernetes): guard resize without pod QoS cgroups

## ENG-219: resize admission guard and migration support

### Problem

Older collection releases joined kubelets with:

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

Kubeadm stores these arguments in `/var/lib/kubelet/kubeadm-flags.env` and does not normally rewrite them during an upgrade. 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 `pods/resize` request 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 distinct trigger paths:

1. **API-initiated resize**

   An API client updates `pods/resize`. This path can be blocked through admission.

2. **Kubelet-initiated reconciliation**

   Releases containing the behavior from [kubernetes/kubernetes#140387](https://github.com/kubernetes/kubernetes/pull/140387) can reach the same vulnerable path internally. Admission cannot intercept this case, so these releases must remain hard-denied until they contain the upstream fix.

### Safety model

This change deliberately keeps both protections:

- A hard version denylist for releases where kubelet-initiated reconciliation can trigger the panic.
- A `ValidatingAdmissionPolicy` for affected releases where explicit API resize is the remaining trigger.

The admission policy:

- matches only `UPDATE` requests to `pods/resize`;
- leaves ordinary Pod updates unaffected;
- uses `failurePolicy: Fail`;
- is created before its binding;
- removes the binding before removing the policy;
- remains installed while any Kubernetes node lacks pod QoS cgroups.

The guard is installed after the control plane reaches the target version and before existing kubelets are upgraded. This avoids a window where the API accepts resize requests while vulnerable kubelets are running.

### Full-inventory detection

The upgrade preflight now evaluates every host in the configured Kubernetes inventory group, even when Ansible is invoked with `--limit`.

For each node it inspects:

- `/var/lib/kubelet/kubeadm-flags.env`;
- `/etc/default/kubelet`;
- `/var/lib/kubelet/config.yaml`;
- the installed kubelet version;
- host-specific `kubernetes_kubeadm_extra_args`;
- host-specific `kubernetes_kubeadm_patches`.

Existing kubelet flags take precedence because kubeadm preserves them across upgrades. Inventory values are used as a fallback for nodes that have not joined yet. An unknown installed kubelet version is treated conservatively as affected.

The play fails if any required node cannot be inspected. It will not remove a cluster-wide safety policy based on incomplete evidence from a limited play.

### Policy lifecycle

The collection creates:

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

The policy is required when either:

- the target Kubernetes version is in an affected resize range and at least one node lacks pod QoS cgroups; or
- an installed kubelet on a legacy node is still in an affected range, including during control-plane-only, limited, or interrupted upgrades.

It is removed only after every node uses pod QoS cgroups, or when both the target version and every installed kubelet on a remaining legacy node are outside the affected ranges. An unknown installed version keeps the policy.

The affected ranges are represented per Kubernetes minor. This allows each branch to be opened independently when the upstream fix becomes available in that branch.

### CI coverage

A dedicated non-voting Zuul upgrade scenario has been added for a `1.34.9 -> 1.35.6` transition.

The scenario deliberately bootstraps the old release with legacy kubelet arguments and then verifies that:

- the admission policy and binding are installed;
- ordinary Pod metadata updates continue to work;
- an explicit `pods/resize` request is rejected by the expected policy;
- the rejected request does not modify the Pod resources;
- the resize probe does not restart a kubelet;
- the existing upgrade canaries remain running.

### Validation completed

Local validation:

- `183` unit tests passed.
- YAML lint passed for all changed YAML files.
- The Molecule verification playbook passed syntax validation.
- `git diff --check` passed.
- Check mode was exercised with a limited inventory and still inspected the complete Kubernetes node group.

A separate multi-node Kubernetes 1.36.2 rehearsal exercised the documented migration against one legacy worker:

1. Drain the worker.
2. Run `kubeadm reset --force`.
3. Delete the stale Node API object.
4. Reapply the collection with `--limit` for that inventory host.
5. Wait for the replacement Node object to become Ready.
6. Schedule a Burstable workload onto the rebuilt node.
7. Verify its QoS cgroup placement.
8. Attempt an in-place resize.
9. Verify the admission denial.
10. Rerun the play in check mode.

Observed results:

- The node rejoined successfully.
- The rebuilt kubelet no longer contained either legacy argument.
- The Burstable workload was placed under the expected `/kubepods/burstable/...` hierarchy.
- The resize request was rejected by `vexxhost-kubelet-resize-guard`.
- The final limited check-mode run reported no changes.
- The cluster remained healthy after the rehearsal.
- The policy remained installed because other intentionally unmigrated legacy nodes were still present.

### Operational documentation

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

- migrate workers before control-plane nodes;
- process only one node at a time;
- preserve application and etcd quorum;
- drain, reset and rejoin rather than editing kubelet flags in place;
- verify kubelet flags, workload readiness and restart behavior;
- remove the guard only after all nodes use pod QoS cgroups;
- recover or roll back a failed migration without proceeding to another node.

The migration is intentionally separate from a Kubernetes version upgrade. Operators should first migrate every node on a safe patch release, verify the cluster, and only then continue the Kubernetes upgrade.
      patchset: e9230d571cd70c3ad348f19c4756339ca0721b55
      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: e32aba41d8c56949186b63be5ae6dea3cc72b035
          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: e32aba41d8c56949186b63be5ae6dea3cc72b035
          untrusted/project_3/github.com/vexxhost/ansible-collection-kubernetes:
            canonical_name: github.com/vexxhost/ansible-collection-kubernetes
            checkout: main
            commit: 65b90e8294d40249aa166b0382567d0dfa04d798
          untrusted/project_4/opendev.org/openstack/openstack-helm:
            canonical_name: opendev.org/openstack/openstack-helm
            checkout: master
            commit: 5030d8eb0fc4be036bc766b051a02cb46e7e152f
        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: 65b90e8294d40249aa166b0382567d0dfa04d798
          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
