You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We ran popeye with cluster-admin permissions in our 1.13 EKS cluster and it claims all service accounts in our cluster reference a secret that does not exist. Snippet of the output:
· kube-system/external-dns.......................................................................💥
💥 [POP-304] References a secret "external-dns-token-tb78n" which does not exists.
· kube-system/fluentd-elasticsearch..............................................................💥
💥 [POP-304] References a secret "fluentd-elasticsearch-token-hq72l" which does not exists.
· kube-system/generic-garbage-collector..........................................................💥
💥 [POP-304] References a secret "generic-garbage-collector-token-cnlpn" which does not exists.
But looking in the kube-system namespace, the secrets are there:
@atheiman Thank you for this excellent report for both the details and the quality of this find!!
I think I've resolved this issue and will push a Popeye update. Great find!!
We ran popeye with
cluster-admin
permissions in our 1.13 EKS cluster and it claims all service accounts in our cluster reference a secret that does not exist. Snippet of the output:But looking in the
kube-system
namespace, the secrets are there:Not sure if its useful, but we invoke
popeye
(usingcluster-admin
ClusterRole) like this:Popeye version:
Kubernetes cluster version:
I think the issue is somewhere in here, but I don't know enough Go to figure it out :(
popeye/internal/sanitize/sa.go
Lines 86 to 93 in 15fd321
The text was updated successfully, but these errors were encountered: