Validated on release-1.31 branch with commit `2b53c7e`

Validation

$ k3s -v
k3s version v1.31.12-rc1+k3s1 (2b53c7e4)
go version go1.23.11

$ sudo journalctl -u k3s | grep -i "Node and Certificate Authority"
Aug 15 17:07:56 ip-172-31-24-23 k3s[7599]: I0815 17:07:56.715304    7599 event.go:389] "Event occurred" object="server1" fieldPath="" kind="Node" apiVersion="" type="Normal" reason="CertificateExpirationOK" message="Node and Certificate Authority certificates managed by k3s are OK"

$ kubectl describe node | grep k3s-cert-monitor
DEBU[0000] Asset dir /var/lib/rancher/k3s/data/fd8ccc572debd9341d83f3a55e8d6d43d8a955d2e2be79302ecfcf439f1563ca
DEBU[0000] Running /var/lib/rancher/k3s/data/fd8ccc572debd9341d83f3a55e8d6d43d8a955d2e2be79302ecfcf439f1563ca/bin/kubectl [kubectl describe node]
  Normal  CertificateExpirationOK         116s                 k3s-cert-monitor       Node and Certificate Authority certificates managed by k3s are OK

Validated on release-1.31 branch with commit 2b53c7e

Validation

Validated on release-1.31 branch with commit `2b53c7e`

[Release-1.31] - Certificate expiration events persist after certificates are rotated #12648

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions