CI: connectivity test - allocator error: unable to create secondary key #42922
Description
CI failure
First seen on Nov 10 in this workflow run, it has become very frequent in Conformance Cluster Mesh and Cilium Cluster Mesh upgrade but as also seen in Conformance IPsec E2E (ci-ipsec-e2e).
2025-11-10T19:36:41.373444588Z level=warn source=/go/src/github.com/cilium/cilium/pkg/allocator/allocator.go:764 msg="Key allocation attempt failed" module=agent.controlplane.identity.identity subsys=allocator error="unable to create secondary key 'k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system;k8s:io.cilium.k8s.policy.cluster=cluster2;k8s:io.cilium.k8s.policy.serviceaccount=coredns;k8s:io.kubernetes.pod.namespace=kube-system;k8s:k8s-app=kube-dns;': identity (id:\"16733298\",key:\"[k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system k8s:io.cilium.k8s.policy.cluster=cluster2 k8s:io.cilium.k8s.policy.serviceaccount=coredns k8s:io.kubernetes.pod.namespace=kube-system k8s:k8s-app=kube-dns]\") does not exist" key="[k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system k8s:io.cilium.k8s.policy.cluster=cluster2 k8s:io.cilium.k8s.policy.serviceaccount=coredns k8s:io.kubernetes.pod.namespace=kube-system k8s:k8s-app=kube-dns]" attempt=0 (2 occurrences)
Recent hits: