studio/meet
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
f9233c8fb3a8a67fa688de306a531a8c4e118e7f
meet/src/helm/helmfile.yaml

119 lines
3.3 KiB
YAML
Raw Normal View History

🚨(helm) fix linter errors Initial set-up errors. Fixed them. Removed unused Preprod environment, as secrets are not configured yet, it raises an error.
2024-09-23 18:31:05 +02:00
environments:
dev:
values:
- version: 0.0.1
secrets:
- env.d/{{ .Environment.Name }}/secrets.enc.yaml
staging:
values:
- version: 0.0.1
addRedirect: True
enablePermanentRedirect: True
oldDomain: meet-staging.beta.numerique.gouv.fr
newDomain: visio-staging.beta.numerique.gouv.fr
secrets:
- env.d/{{ .Environment.Name }}/secrets.enc.yaml
production:
values:
- version: 0.0.1
addRedirect: True
enablePermanentRedirect: True
oldDomain: meet.numerique.gouv.fr
newDomain: visio.numerique.gouv.fr
secrets:
- env.d/{{ .Environment.Name }}/secrets.enc.yaml
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
repositories:
- name: bitnami
url: registry-1.docker.io/bitnamicharts
oci: true
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
- name: livekit
url: https://helm.livekit.io
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
releases:
- name: postgres
installed: {{ eq .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
chart: bitnami/postgresql
version: 13.1.5
values:
- auth:
username: dinum
password: pass
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
database: meet
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
- tls:
enabled: true
autoGenerated: true
✨(backend) add S3 objects Inspired by Impress and @sampaccoud's work. We use Indie Hoster’s Kubernetes objects in staging and production. In the "dev" environment, we install the `bitnami/minio` chart to mimic Indie Hoster’s MinIO setup. To access the MinIO admin interface in dev, use port forwarding; the interface runs on port 9001.
2024-10-25 12:22:41 +02:00
- name: minio
installed: {{ eq .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
chart: bitnami/minio
version: 12.10.10
values:
- auth:
rootUser: meet
rootPassword: password
- provisioning:
enabled: true
buckets:
- name: meet-media-storage
versioning: true
🔧(helm) expose MinIO console via ingress Add ingress configuration for MinIO web console access. Include Nginx proxy buffer annotations to support large file uploads through web interface.
2024-11-04 15:11:11 +01:00
- ingress:
enabled: true
hostname: minio-console.127.0.0.1.nip.io
servicePort: 9001
annotations:
nginx.ingress.kubernetes.io/proxy-body-size: "0"
kubernetes.io/ingress.class: nginx
✨(backend) add S3 objects Inspired by Impress and @sampaccoud's work. We use Indie Hoster’s Kubernetes objects in staging and production. In the "dev" environment, we install the `bitnami/minio` chart to mimic Indie Hoster’s MinIO setup. To access the MinIO admin interface in dev, use port forwarding; the interface runs on port 9001.
2024-10-25 12:22:41 +02:00
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
- name: redis
installed: {{ eq .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
chart: bitnami/redis
version: 18.19.2
values:
- auth:
password: pass
architecture: standalone
- name: extra
installed: {{ ne .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
chart: ./extra
secrets:
- env.d/{{ .Environment.Name }}/secrets.enc.yaml
🔒️(helm) setup temporary redirect Add a specific certificate to prepare redirect
2024-09-23 09:48:14 +02:00
values:
- env.d/{{ .Environment.Name }}/values.meet.yaml.gotmpl
- addRedirect: {{ .Values | get "addRedirect" "False" }}
enablePermanentRedirect: {{ .Values | get "enablePermanentRedirect" "False"}}
oldDomain: {{ .Values | get "oldDomain" "demo.com" }}
newDomain: {{ .Values | get "newDomain" "demo.com" }}
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
- name: meet
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
version: {{ .Values.version }}
namespace: {{ .Namespace }}
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
chart: ./meet
values:
- env.d/{{ .Environment.Name }}/values.meet.yaml.gotmpl
secrets:
- env.d/{{ .Environment.Name }}/secrets.enc.yaml
- name: livekit
installed: {{ eq .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
chart: livekit/livekit-server
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
values:
🔧(helm) adapt helm chart Done: - Rename all occurrences of "impress" to "meet". - Update Agent Connect secrets credentials for the dev environment. - Add new development secrets for LiveKit. - Remove Minio from the dev stack (no cold storage required). - Add LiveKit chart to the stack. - Remove templates and values related to the WebSocket server. The integration of LiveKit was inspired by an example from the "numerique-gouve/infrastructure" repo. However, a notable issue persists with LiveKit's default chart: we are unable to override the namespace, resulting in all LiveKit components running in the default namespace. thx to @rouja for his help.
2024-07-02 19:36:09 +02:00
- env.d/{{ .Environment.Name }}/values.livekit.yaml.gotmpl
✨(project) Django boilerplate This commit introduces a boilerplate inspired by https://github.com/numerique-gouv/impress. The code has been cleaned to remove unnecessary Impress logic and dependencies. Changes made: - Removed Minio, WebRTC, and create bucket from the stack. - Removed the Next.js frontend (it will be replaced by Vite). - Cleaned up impress-specific backend logics. The whole stack remains functional: - All tests pass. - Linter checks pass. - Agent Connexion sources are already set-up. Why clear out the code? To adhere to the KISS principle, we aim to maintain a minimalist codebase. Cloning Impress allowed us to quickly inherit its code quality tools and deployment configurations for staging, pre-production, and production environments. What’s broken? - The tsclient is not functional anymore. - Some make commands need to be fixed. - Helm sources are outdated. - Naming across the project sources are inconsistent (impress, visio, etc.) - CI is not configured properly. This list might be incomplete. Let's grind it.
2024-01-09 15:30:36 +01:00
secrets:
- env.d/{{ .Environment.Name }}/secrets.enc.yaml
✨(livekit) add Livekit Egress Egress is already deployed in staging. But, while working locally on feature relying on Egress, it's not suitable to test your development or iterate. Especially I'll need to test the connection between the Egress and the minio bucket in my next PR. We faced quite a few issue while starting the whole stack. Egress didn't want to start. Its connection with the livekit server while the egress participant was joining the room was not successful. The Turn part of the livekit server helm chart was activated. We needed to update few values to in the helm configuration to enabled this turn. Updated CoreDNS to expose Egress pod. Egress tries connecting to MinIO at 127.0.0.1, where no instance exists. Using minio.127.0.0.1.nip.io resolves to 127.0.0.1, causing Egress to connect to itself for uploads. The CoreDNS rewrite directs this to the Ingress IP, correctly routing to MinIO.
2024-10-25 13:58:15 +02:00
- name: livekit-egress
installed: {{ eq .Environment.Name "dev" | toYaml }}
namespace: {{ .Namespace }}
chart: livekit/egress
values:
- env.d/{{ .Environment.Name }}/values.egress.yaml.gotmpl
secrets:
- env.d/{{ .Environment.Name }}/secrets.enc.yaml
Reference in New Issue Copy Permalink