This message was deleted.
# k3sa
adamant-kite-43734
09/16/2022, 11:38 PMThis message was deleted.
b
bitter-furniture-26042
09/16/2022, 11:38 PMSo, I'm following this documentation: https://argoproj.github.io/argo-workflows/access-token/
c
creamy-pencil-82913
09/16/2022, 11:40 PMDid you see the comment at the bottom about how those instructions are incomplete as of Kubernetes 1.24?
b
bitter-furniture-26042
09/16/2022, 11:40 PMI created the role, then created the serviceaccount, then the rolebinding. However, when I try to get the secret for that account, there's none. Shouldn't this token be created automatically and saved as a Secret? If not, then do you guys know how to create one?
bitter-furniture-26042
09/16/2022, 11:40 PMOhhhhhh... thanks a lot @creamy-pencil-82913, I overlooked that, sorry!
bitter-furniture-26042
09/16/2022, 11:45 PMI'm in a bit of a bad situation now, don't know how to solve it: I need to keep using kubectl 1.23 (for company reasons), and with that version there's no
create tokenc
creamy-pencil-82913
09/16/2022, 11:57 PMyou’re using a 1.24 server but are stuck with a 1.23 client?
creamy-pencil-82913
09/16/2022, 11:58 PMDo you not have access to the k3s nodes? If you’re using a k3s 1.24 release, it comes with the same version of kubectl…
b
bitter-furniture-26042
09/17/2022, 12:10 AMExactly, that's the version difference I have...
Actually, I haven't thought about using k3s 's kubectl itself, I'll try that, good idea!
bitter-furniture-26042
09/17/2022, 5:34 AMSeems to have worked, thanks! 🙂