Replies: 4 comments 4 replies
-
I don't know what that's coming from, but it's not RKE2. As far as I know we don't create nor do we look for a configmap by that name. You have the audit logs, can you tell what's requesting it, and what type of requests those are (get/watch/etc)? |
Beta Was this translation helpful? Give feedback.
-
This is the content of the rke2 config map:
and this is the complete audit event:
|
Beta Was this translation helpful? Give feedback.
-
A cluster with 4 nodes, all rke2 server, version 1.25.9, something keeps etcd pretty busy:
|
Beta Was this translation helpful? Give feedback.
-
This is all normal given the version you're on. Kubernetes 1.25 uses the ConfigMapsLeasesResourceLock type by default. Newer versions will use pure Leases instead, as the legacy lock types become deprecated. You'll still see the same amount of traffic to the leader election resources, but they'll be Leases instead of ConfigMaps.
Is there an actual problem that you're trying to solve? |
Beta Was this translation helpful? Give feedback.
-
Hello,
grep in kube-api audit log, I can see that there is huge number of calls for rke2 configmap:
is this something expected to be happening on 36 node cluster? (rke2 1.24.13)
the output is result from command:
Beta Was this translation helpful? Give feedback.
All reactions