This message was deleted.
# fleeta
adamant-kite-43734
06/08/2022, 4:03 PMThis message was deleted.
p
powerful-florist-21503
06/08/2022, 4:18 PMEKS kubernetes version 1.21
powerful-florist-21503
06/08/2022, 4:26 PMIs this the “same” problem 🤔https://github.com/prometheus-community/helm-charts/issues/1835
g
great-bear-19718
06/09/2022, 6:46 AMare you running standalone fleet or rancher on the EKS cluster?
great-bear-19718
06/09/2022, 6:53 AMtbh.. i have managed eks clusters with rancher and have not seen this error but cant be sure
p
powerful-florist-21503
06/09/2022, 7:06 AMRancher on EKS 1.21
powerful-florist-21503
06/09/2022, 7:21 AMHmmh, managed to workaround this by running the fleet pod as a root:
securityContext:
runAsUser: 0
g
great-bear-19718
06/09/2022, 7:24 AMare you please also able to log a GH issue so we can track the same as well
p
powerful-florist-21503
06/09/2022, 7:25 AMBut still, workaround is a hack, I edited existing pod yaml and applied modified with kubectl. I was also unable to modify the Job, it could not be edited. To me this definately feels like a bug in Rancher Fleet working in EKS.
g
great-bear-19718
06/09/2022, 7:25 AMwell i cant say until we have had a look
great-bear-19718
06/09/2022, 7:26 AMneed to check what EKS is doing differently because from k8s version perspective 1.21 is supported
p
powerful-florist-21503
06/09/2022, 7:27 AMWill make an issue to GH when I have some time, busy day today.
powerful-florist-21503
06/09/2022, 7:28 AMSomething related to service accounts is changed in EKS with 1.21 https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#kubernetes-1.21
powerful-florist-21503
06/09/2022, 8:35 AM@great-bear-19718 Issue created to GH https://github.com/rancher/fleet/issues/790
👍 1
137 Views