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

🔧(helm) multiple changes for deploying with stack #215

Closed
wants to merge 4 commits into from

Conversation

wilbrdt
Copy link
Contributor

@wilbrdt wilbrdt commented Feb 26, 2024

Proposal

Naming convention

  • Some templates follows the snake_case naming convention. Renaming them to kebab-case.

Secrets and configmaps

  • Now that we use Hashicorp Vault for managing secrets, we can now create secrets to store sensitive environment variables within the chart. Additionally, non-sensitive environment variables are now appropriately segregated withing configmaps (api/app env, database and logging).

Minor lint issue

  • Fixing the lint issue by only adding an httpHeaders if value allowHosts is not empty, for both api and app deployments.

Migration and staticfiles collection jobs

  • Using pre-install Helm hooks for migrating the database and collecting static files before a deployment. Another solution would have been an initContainer inside the deployment, either executing the migration/collection, or waiting for jobs doing the migration/collection.

@wilbrdt wilbrdt added the helm label Feb 26, 2024
@wilbrdt wilbrdt requested a review from jmaupetit February 26, 2024 17:39
@wilbrdt wilbrdt self-assigned this Feb 26, 2024
Copy link

changeset-bot bot commented Feb 26, 2024

⚠️ No Changeset found

Latest commit: 8986e5d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@wilbrdt wilbrdt marked this pull request as draft February 27, 2024 09:26
@wilbrdt wilbrdt changed the title 🔧(helm) move all non-secret env variables to a config map 🔧(helm) multiple changes for deploying with stack Mar 1, 2024
@wilbrdt wilbrdt force-pushed the helm/tweaks branch 3 times, most recently from c8c9f75 to 8986e5d Compare March 4, 2024 11:25
@wilbrdt wilbrdt marked this pull request as ready for review March 4, 2024 11:25
@wilbrdt wilbrdt removed the request for review from jmaupetit April 3, 2024 14:28
wilbrdt added 4 commits April 5, 2024 10:21
Helm template files naming generally follows the kebab-case naming convention.
Renaming Warren helm template files to follow it.
Now that we use Hashicorp Vault for managing secrets, we can now create secrets
to store sensitive environment variables within the chart.
Additionally, non-sensitive environment variables are now appropriately
segregated withing configmaps (api/app env, database and logging).
On liveness and readiness probes, with virtual hosts, `Host` should be set in
the Host header. As the default value is an empty list, Helm linter was raising
an error.
Fixing the lint issue by only adding an `httpHeaders` if value `allowHosts` is
not empty, for both `api` and `app` deployments.
As it is generally recommended to handle databases outside the cluster,
disabling the postgresql database deployment by default.
@wilbrdt
Copy link
Contributor Author

wilbrdt commented May 17, 2024

Closing as work is done on #252

@wilbrdt wilbrdt closed this May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant