Greg Kogan

FYI, as a workaround, you can add the following to the master IG ``` additionalUserData: - content: |- #!/bin/sh chmod 666 /srv/kubernetes/aws-iam-authenticator/*.pem name: z_aws-iam-authenticator-fix-permission.sh type: text/x-shellscript ```

No, it was the default ubuntu ami, but for arm64 which should not make a difference in theory. The only thing that might be different is that I was enabling...

I believe this commit should fix the issue: https://github.com/kubernetes/kops/commit/74310774f1805b9d48a2f308948ce3b71a25b56d My daemonset did not have it, but it was created with 1.23 and this commit is for the 1.24.x, so _maybe_...

I will be provisioning a new cluster in a day or so, so I will try to report back, but I do think it should work. BTW, I noticed another...

Which one? The main issue I reported is not related to the actual aws-iam-authenticator image so changing it will not make a difference. Also, I do not believe I saw...

We ended up switching to using the Syslog (specifically syslog-ng) for our kubernetes setup. It actually slightly improves logging by converting syslog messages to json and printing them to stdout....

Referencing an environment variable may be an easier lift, but unless there is a good way to inject credentials, the whole file needs to be stored as a Kubernetes secret...