studio/people
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
This repository has been archived on 2026-03-24. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
0a8c488649697f0c4609e7a39b00a883d3a42e1a
people/src/helm/helmfile.yaml

59 lines
1.5 KiB
YAML
Raw Normal View History

🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
repositories:
- name: bitnami
url: registry-1.docker.io/bitnamicharts
oci: true
releases:
- name: postgres
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
installed: {{ eq .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
chart: bitnami/postgresql
version: 13.1.5
values:
- auth:
username: dinum
password: pass
database: people
- tls:
enabled: true
autoGenerated: true
🚀(helm) add a Redis cache service This commit is working in progress. I have added an extra chart to take benefits of the Redis operator developed by Indie hoster. When using the dev environment, I used bitnami redis chart to deploy a Redis service with authentication disable.
2024-03-19 13:36:50 +01:00
- name: redis
installed: {{ eq .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
chart: bitnami/redis
version: 18.19.2
values:
- auth:
password: pass
🔨(CI) add Tilt Tilt is a tool for local Kubernetes development. It makes it easy to see your changes as you make them, and it rebuilds and redeploys your app as you change it.
2024-06-03 10:05:45 +02:00
architecture: standalone
🚀(helm) add a Redis cache service This commit is working in progress. I have added an extra chart to take benefits of the Redis operator developed by Indie hoster. When using the dev environment, I used bitnami redis chart to deploy a Redis service with authentication disable.
2024-03-19 13:36:50 +01:00
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
- name: extra
installed: {{ ne .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
chart: ./extra
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-04-23 10:53:38 +02:00
secrets:
💚(ci) remove secret from repository - Remove *.enc.* - Adapt helmfile - Adapt CI
2024-06-07 08:56:23 +02:00
- {{ ne .Environment.Name "dev" | ternary "secrets/numerique-gouv/people/env" "env.d" }}/{{ .Environment.Name }}/secrets.enc.yaml
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
- name: desk
version: {{ .Values.version }}
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
namespace: {{ .Namespace }}
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
chart: ./desk
values:
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
- env.d/{{ .Environment.Name }}/values.desk.yaml.gotmpl
secrets:
💚(ci) remove secret from repository - Remove *.enc.* - Adapt helmfile - Adapt CI
2024-06-07 08:56:23 +02:00
- {{ ne .Environment.Name "dev" | ternary "secrets/numerique-gouv/people/env" "env.d" }}/{{ .Environment.Name }}/secrets.enc.yaml
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
environments:
dev:
values:
- version: 0.0.1
🔐(helm) add OIDC secrets for dev environment Set OIDC secrets for the dev environment. Please note that we use different secrets between dev and staging. Why? Benoit created two client id, thus we could easily tests Agent Connect feature from the local host and the staging one. The local host is desk.127.0.0.1.nip.io. If this value change at any time, please consider asking Benoit to update the host value linked to the dev client id.
2024-03-18 23:27:30 +01:00
secrets:
- env.d/{{ .Environment.Name }}/secrets.enc.yaml
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
staging:
values:
- version: 0.0.1
secrets:
💚(ci) remove secret from repository - Remove *.enc.* - Adapt helmfile - Adapt CI
2024-06-07 08:56:23 +02:00
- {{ ne .Environment.Name "dev" | ternary "secrets/numerique-gouv/people/env" "env.d" }}/{{ .Environment.Name }}/secrets.enc.yaml
🚀(helm) build a minimalistic dev Helmfile Please note that this Helmfile is uncomplete, it lacks services as redis, celery, mail ... which are declared in the Docker Compose file but not yet used in development and production images. Thus, to run the Desk Helm chart, we only add a postgres database to run the Django backend server, and apply migrations. For now, this Helmfile is quite hard to test in dev environment, because the frontend redirects automatically to the SSO login page. We cannot really assess if backend and frontend are working properly. We might adjust some configurations after the first deployment in stagging. (We are a bit in rush, to respect the current sprint deadline.) Development values points https://desk.127.0.0.1.nip.io URL. Please note that the frontend image for now has been built with this URL for the backend address. Meaning that we either need to rebuild and publish a frontend image with the staging URL when deploying the project, or enhance our frontend image, to pass the backend URL at runtime.
2024-03-14 18:11:06 +01:00
Reference in New Issue Copy Permalink