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

35 lines
904 B
YAML
Raw Normal View History

feat: initial commit
2023-01-25 20:27:27 +01:00
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- ./resources/hydra-deployment.yaml
- ./resources/hydra-service.yaml
- ./resources/hydra-role.yaml
- ./resources/hydra-rolebinding.yaml
- ./resources/hydra-serviceaccount.yaml
- ./resources/hydra-migrate-job.yaml
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-maester
feat: initial commit
2023-01-25 20:27:27 +01:00
secretGenerator:
- name: hydra-secret
literals:
- SECRETS_SYSTEM=ThisShouldBeAbsolutelyChanged
configMapGenerator:
- name: hydra-env
literals:
- URLS_SELF_ISSUER=http://localhost:4444
- URLS_LOGIN=http://hydra-login-app/login
- URLS_CONSENT=http://hydra-consent-app/consent
- URLS_LOGOUT=http://hydra-logout-app/logout
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_SERVE_ALL_ARGS=--dev
feat(hydra): adding new literal to configmap hydra-env
2023-03-15 12:15:48 +01:00
- LOG_LEVEL=info
fix: use variable to reference hydra-migrate job
2023-01-30 16:15:39 +01:00
vars:
- name: HYDRA_MIGRATE_JOB_NAME
objref:
name: hydra-migrate
kind: Job
apiVersion: batch/v1
fieldref:
fieldpath: metadata.name