Philippe Caseiro
8075071f22
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.
35 lines
904 B
YAML
35 lines
904 B
YAML
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
|
|
- ./resources/hydra-maester
|
|
|
|
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
|
|
- HYDRA_SERVE_ALL_ARGS=--dev
|
|
- LOG_LEVEL=info
|
|
|
|
vars:
|
|
- name: HYDRA_MIGRATE_JOB_NAME
|
|
objref:
|
|
name: hydra-migrate
|
|
kind: Job
|
|
apiVersion: batch/v1
|
|
fieldref:
|
|
fieldpath: metadata.name |