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

51 lines
936 B
YAML
Raw Permalink Normal View History

feat: initial commit
2023-01-25 20:27:27 +01:00
apiVersion: kustomize.config.k8s.io/v1alpha1
kind: Component
configurations:
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
- ./configurations/cnpg-cluster.yaml
feat: initial commit
2023-01-25 20:27:27 +01:00
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-cnpg-cluster.yaml
feat: initial commit
2023-01-25 20:27:27 +01:00
secretGenerator:
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-postgres-admin
type: Secret
literals:
- username=postgres
- password=NotSoSecret
- name: hydra-postgres-user
type: Secret
literals:
- username=hydra
- password=NotSoSecret
feat: initial commit
2023-01-25 20:27:27 +01:00
fix: use variable to determine postgresql service name
2023-01-30 16:38:56 +01:00
vars:
- name: HYDRA_DATABASE_SERVICE_NAME
objref:
name: hydra-postgres
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
kind: Cluster
fix: use variable to determine postgresql service name
2023-01-30 16:38:56 +01:00
apiVersion: postgresql.cnpg.io/v1
fieldref:
fieldpath: metadata.name
feat(hydra): add janitor cronjob
2023-12-11 10:45:22 +01:00
patches:
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
- target:
group: apps
version: v1
kind: Deployment
name: hydra
path: patches/hydra-deployment.yaml
- target:
group: batch
version: v1
kind: Job
name: hydra-migrate
path: patches/hydra-migrate-job.yaml
feat(hydra): add janitor cronjob
2023-12-11 10:45:22 +01:00
- target:
group: batch
version: v1
kind: CronJob
name: hydra-janitor
path: patches/hydra-janitor-cronjob.yaml