chore(deps): update reg.kyverno.io/kyverno/kyverno docker tag to v1.18.1

[renovate]

This PR contains the following updates:

Package	Update	Change
reg.kyverno.io/kyverno/kyverno	patch	v1.18.0 → v1.18.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Caution

🩺 Integration diagnosis — mode: fresh, phase: install

Commit: 15455e7 · Run: #26289335004

Likely cause: The CI runner's disk reached the kubelet eviction threshold within ~94 seconds of node boot, applying a node.kubernetes.io/disk-pressure:NoSchedule taint that blocked all Deployment-managed pods from scheduling and stalled the cluster health checks.

Evidence: Node controlplane-1 acquired taint node.kubernetes.io/disk-pressure:NoSchedule at 13:05:44 UTC (boot completed at 13:04:10). Pods coredns (0/2 replicas), kubelet-serving-cert-approver (0/1 replicas), and flux2-flux-check all reported FailedScheduling with no nodes available to schedule pods / 1 node(s) had untolerated taint(s). Without kubelet-serving-cert-approver running, CSR csr-rvz4n (the kubelet serving cert for system:node:controlplane-1) remained unapproved, causing the kubelet API endpoint to reject connections with remote error: tls: internal error — logged repeatedly from 13:05:23 onward. The disk pressure arrived before Flux or Kyverno were ever deployed, so the PR's single-line image tag bump (reg.kyverno.io/kyverno/kyverno v1.18.0 → v1.18.1) could not have caused the failure.

Suggested next step: Re-run the workflow — this is a transient CI runner resource failure unrelated to PR changes; if it recurs consistently, investigate whether the Docker storage configuration step in the CI workflow is providing sufficient disk headroom before Talos node boot.

Live read-only inspection by Claude. Support bundle attached to the run artifacts.