CadolesKube
/
sso-kustom
14
0
Fork 0
Code Issues 19 Pull Requests 4 Projects Releases Wiki Activity
sso-kustom/resources/hydra-dispatcher/kustomization.yaml

41 lines
1.0 KiB
YAML
Raw Permalink Normal View History

feat: initial commit
2023-01-25 20:27:27 +01:00
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
feat(resource): adding new hydra-maester resource This allow to manage "Clients" with a CRD from official doc: The controller listens for Custom Resource which defines client registration request. Once Custom resource is created, the controller register oauth2 client in hydra using hydra's REST API. Client Id, Client Secret and Identifier of the client in hydra are be stored in the kubernetes as a secret and referenced in the applied CR. Reference is used to identify in which kubernetes secret are stored mentioned properties. Secret iscreated in the same namespace of applied CR. By default controller should be deployed in the same pod as hydra. Service discovery will come in place in the future.
2023-03-17 11:05:23 +01:00
- ./resources/hydra-dispatcher-deployment.yaml
- ./resources/hydra-dispatcher-service.yaml
feat: initial commit
2023-01-25 20:27:27 +01:00
Patche du DSN redis
2023-12-18 10:38:13 +01:00
generatorOptions:
labels:
com.cadoles.forge.sso-kustom/session: redis
feat: initial commit
2023-01-25 20:27:27 +01:00
configMapGenerator:
feat(resource): adding new hydra-maester resource This allow to manage "Clients" with a CRD from official doc: The controller listens for Custom Resource which defines client registration request. Once Custom resource is created, the controller register oauth2 client in hydra using hydra's REST API. Client Id, Client Secret and Identifier of the client in hydra are be stored in the kubernetes as a secret and referenced in the applied CR. Reference is used to identify in which kubernetes secret are stored mentioned properties. Secret iscreated in the same namespace of applied CR. By default controller should be deployed in the same pod as hydra. Service discovery will come in place in the future.
2023-03-17 11:05:23 +01:00
- name: hydra-dispatcher-env
literals:
- APP_ENV=prod
- APP_DEBUG=false
Utilisation images symfony-containers
2023-06-28 10:14:26 +02:00
- PHP_FPM_MEMORY_LIMIT=256m
- NGINX_APP_SERVER_LISTEN=80
feat(resource): adding new hydra-maester resource This allow to manage "Clients" with a CRD from official doc: The controller listens for Custom Resource which defines client registration request. Once Custom resource is created, the controller register oauth2 client in hydra using hydra's REST API. Client Id, Client Secret and Identifier of the client in hydra are be stored in the kubernetes as a secret and referenced in the applied CR. Reference is used to identify in which kubernetes secret are stored mentioned properties. Secret iscreated in the same namespace of applied CR. By default controller should be deployed in the same pod as hydra. Service discovery will come in place in the future.
2023-03-17 11:05:23 +01:00
- HYDRA_BASE_URL=http://hydra:4444
- HYDRA_ADMIN_BASE_URL=http://hydra:4445
- HYDRA_REWRITE_ISSUER=yes
- HYDRA_ORIGINAL_ISSUER=http://hydra:4444
- HYDRA_NEW_ISSUER=http://hydra-dispatcher
- BASE_URL=http://hydra-dispatcher
- COOKIE_PATH=/
- DEFAULT_LOCALE=fr
- APP_LOCALES=fr,en
Patche du DSN redis
2023-12-18 10:38:13 +01:00
- REDIS_DSN="redis://redis:6379"
feat: add xdebug to dispatcher and sql
2024-10-04 15:52:04 +02:00
- OPCACHE_VALIDATE_TIMESTAMP="0"
- OPCACHE_REVALIDATE_FREQ="0"
- XDEBUG_MODE=off
feat(resource): adding new hydra-maester resource This allow to manage "Clients" with a CRD from official doc: The controller listens for Custom Resource which defines client registration request. Once Custom resource is created, the controller register oauth2 client in hydra using hydra's REST API. Client Id, Client Secret and Identifier of the client in hydra are be stored in the kubernetes as a secret and referenced in the applied CR. Reference is used to identify in which kubernetes secret are stored mentioned properties. Secret iscreated in the same namespace of applied CR. By default controller should be deployed in the same pod as hydra. Service discovery will come in place in the future.
2023-03-17 11:05:23 +01:00
- name: hydra-dispatcher-apps
files:
update config default apps filename
2023-07-27 10:49:42 +02:00
- apps.yaml=./files/hydra/default.yaml
Add opcache to symfony apps
2024-08-02 10:33:27 +02:00
- name: hydra-dispatcher-php-ini
files:
feat: add xdebug to dispatcher and sql
2024-10-04 15:52:04 +02:00
- ./files/03_base.ini
- name: xdebug-dispatcher-config
behavior: create
files:
- ./files/50_xdebug.ini