added automountServiceAccountToken flag

[imdmahajankanika]

Pull Request

Related issue

Fixes #<issue_number>

What does this PR do?

• ...

PR checklist

Please check if your PR fulfills the following requirements:

• Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
• Have you read the contributing guidelines?
• Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Summary by CodeRabbit

• New Features
  • Added a new configuration option to control whether Kubernetes service account tokens are automatically mounted on pods
  • Enables administrators to enforce stricter security policies by controlling token availability
  • Default setting is disabled, allowing selective opt-in for deployments requiring service account tokens

[coderabbitai]

Walkthrough

Adds a new configuration field automountServiceAccountToken to the Meilisearch Helm chart, exposing control over automatic ServiceAccount token mounting via the ServiceAccount manifest template with a corresponding default value in values.yaml.

Changes

Cohort / File(s)	Change Summary
ServiceAccount Token Configuration charts/meilisearch/templates/serviceaccount.yaml, charts/meilisearch/values.yaml	Introduces automountServiceAccountToken configuration option for the ServiceAccount manifest. Template field added to conditionally mount the service account token on pods, with default value set to false in values.yaml.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A token's fate, we now control,
With automount, a rabbit's goal,
Security reigns in the chart so bright,
ServiceAccounts configured just right! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "added automountServiceAccountToken flag" accurately and specifically describes the primary change in the changeset. The modifications across both charts/meilisearch/values.yaml and charts/meilisearch/templates/serviceaccount.yaml are centered on introducing a new configuration flag to control automatic mounting of service account tokens. The title is concise, specific to the actual change, and avoids vague language, making it clear to teammates scanning git history what the PR accomplishes.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61146ef and e16a48c.

📒 Files selected for processing (2)

• charts/meilisearch/templates/serviceaccount.yaml (1 hunks)
• charts/meilisearch/values.yaml (1 hunks)

🔇 Additional comments (2)

charts/meilisearch/values.yaml (1)

64-67: Well-documented configuration addition with secure defaults.

The new automountServiceAccountToken flag is properly documented following Helm conventions and defaults to false, which aligns with the security best practice of not auto-mounting the ServiceAccount token unless explicitly needed. Clear documentation explains when users might set this to true.

charts/meilisearch/templates/serviceaccount.yaml (1)

12-12: Code change verified and correct.

The automountServiceAccountToken field at line 12 is correctly positioned at the root level of the ServiceAccount object and properly references serviceAccount.automountServiceAccountToken from values.yaml, which is defined as false. The template will render valid Kubernetes ServiceAccount YAML.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}