-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add service account token secret #160
Conversation
@@ -14,3 +14,11 @@ stringData: | |||
s3BucketName: {{ .Values.daemonset.s3BucketName }} | |||
s3Region: {{ .Values.daemonset.s3Region }} | |||
{{- end }} | |||
--- | |||
apiVersion: v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be put behind a flag such as
{{- if .Values.daemonset.useServiceAccountToken }}
apiVersion: v1
.....
With the value set to false in the values.yaml
https://github.com/IBM/core-dump-handler/blob/main/charts/core-dump-handler/values.yaml#L60
useServiceAccountToken: false
If this is mandatory now for all AWS instances can you set the value set to true in aws.values.yaml
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your feedback! I've moved the secret to a dedicated file and added the flag, but to the serviceAccount
section, seemed more intuitive to me.
Also want to outline, that this does not seem to be limited to AWS (https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md#no-really-you-must-read-this-before-you-upgrade-1). I can't test/verify this for any other environment, have no access to any. But if it turns out it is required, I could add the respective config to the other values files.
Signed-off-by: usimd <11619247+usimd@users.noreply.github.com>
@usimd Thank you very much for this work. |
Thank you for sharing this work, @No9! Much appreciated 👍 Would it be possible to create a new release with this PR in place? Or are there other changes you're waiting for? |
Yes I want to try and land this before the next release |
Hey @No9 👋 |
Hey @usimd |
Hello guys, sorry for the nudge. I understand @No9 you are busy but do you have an estimate when the next release is out. I'm waiting for the fix in this PR. |
Much appreciated @No9 , cheers to everyone working on this project. |
Adds a new secret to be compatible with EKS >= 1.24 (see https://aws.github.io/aws-eks-best-practices/security/docs/iam/).
This closes #143 and closes #140.
Open design questions:
put token secret in dedicated file?make secret name configurable?KubeVersion
?add specific flag to toggle token secret creation?Let me know what you think 😃