Skip to content

Fix secret naming consistency #323

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

Merged
merged 1 commit into from
Mar 31, 2025

Conversation

alaturqua
Copy link
Contributor

Ensure the secret and volume names dynamically use the chart's full name instead of a hardcoded value, aligning with Helm best practices and preventing naming conflicts in multi-instance deployments.

  • Replace static references (trino-gateway-configuration) with templated Helm function ({{ include "trino-gateway.fullname" . }}-configuration).
  • Update secret definition in secrets.yaml.
  • Update volume mounts and secret references in deployment.yaml.

Ensure the secret and volume names dynamically use the chart's full name instead of a hardcoded value, aligning with Helm best practices and preventing naming conflicts in multi-instance deployments.

- Replace static references (`trino-gateway-configuration`) with templated Helm function (`{{ include "trino-gateway.fullname" . }}-configuration`).
- Update secret definition in `secrets.yaml`.
- Update volume mounts and secret references in `deployment.yaml`.
@cla-bot cla-bot bot added the cla-signed label Mar 29, 2025
@nineinchnick nineinchnick added the enhancement New feature or request label Mar 31, 2025
@nineinchnick nineinchnick merged commit c13866e into trinodb:main Mar 31, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed enhancement New feature or request
Development

Successfully merging this pull request may close these issues.

2 participants