Skip to content
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

feat(argo-rollouts): configurable automountServiceAccountToken #3032

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

k-cogswell
Copy link

Inspired by #2625

Adding a configurable option for automountServiceAccountToken in argo-rollouts chart. This is my first contribution so please let me know if I am missing anything.

Checklist:

  • I have bumped the chart version according to versioning
  • I have updated the documentation according to documentation
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.
  • My build is green (troubleshooting builds).

@k-cogswell k-cogswell force-pushed the feat/configurable-automountServiceAccountToken branch from a0706de to 92d7cd0 Compare November 13, 2024 19:43
@k-cogswell k-cogswell changed the title feat: configurable automountServiceAccountToken feat(argo-rollouts): configurable automountServiceAccountToken Nov 13, 2024
Comment on lines 232 to 233
# -- Specifies wether a service account should be automounted
automount: true
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regarding the comment and default value, please align to #2625 .
Reason of the default value false is also mentioned in the PR.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yu-croco The comments and default values have been updated. Thank you for the feedback.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yu-croco looking at the referenced PR again, the default value is set to true.

You can also see in this in main

automountServiceAccountToken: true

If you're okay with this I can revert my values file back to the original value of true,

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, lets use true as the default. Otherwise it would be a breaking change.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad... 🫠 Please revert as true .

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated! Thanks again for your feedback @yu-croco @mkilchhofer

@k-cogswell k-cogswell force-pushed the feat/configurable-automountServiceAccountToken branch 2 times, most recently from 285f4a2 to 401f991 Compare November 14, 2024 12:55
Signed-off-by: Kyle Cogswell <kcogswell26@gmail.com>
@k-cogswell k-cogswell force-pushed the feat/configurable-automountServiceAccountToken branch from 1ea9b3d to e7da93b Compare November 15, 2024 13:12
Copy link
Collaborator

@yu-croco yu-croco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution. LGTM

@@ -44,6 +44,7 @@ spec:
{{- toYaml . | nindent 8 }}
{{- end }}
serviceAccountName: {{ include "argo-rollouts.serviceAccountName" . }}
automountServiceAccountToken: {{ .Values.serviceAccount.automount }}
Copy link
Member

@mkilchhofer mkilchhofer Nov 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we are setting the field on the kind: Deployment rather than on the kind: ServiceAccount can we use {{ .Values.controller.automountServiceAccountToken }} instead?

Background: I'd like to be in line with every chart we provide and this is already implemented in the argo-cd Helm chart.

@@ -45,6 +45,7 @@ spec:
{{- toYaml . | nindent 8 }}
{{- end }}
serviceAccountName: {{ include "argo-rollouts.serviceAccountName" . }}-dashboard
automountServiceAccountToken: {{ .Values.dashboard.serviceAccount.automount }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we are setting the field on the kind: Deployment rather than on the kind: ServiceAccount can we use {{ .Values.dashboard.automountServiceAccountToken }} instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants