Commit Graph

12 Commits

Author SHA1 Message Date
b7b9787ca4 feat(hydra-oidc): non root deployment with caddy 2024-03-27 14:08:58 +01:00
380a116fa8 fix(all): use app.kubernetes.io/name label instead of io.kompose.service 2024-02-21 15:43:42 +01:00
29f539f7ab fix(oidc): removing deprecated and useless patch
fix container liveness and readyness probes
fix service with correct port
2024-02-13 16:49:37 +01:00
a02622b516 feat(hydra): mise en place du stockage des session redis sur la stack hydra, et correction logout sur hydra-oidc 2023-12-15 10:17:23 +01:00
435597f9f1 feat(hydra-dispatcher): update image tag 2023-12-11 10:47:56 +01:00
63c5d7259c add probes 2023-12-11 10:47:56 +01:00
d37e85000f set correct tag for hydra-oidc 2023-12-11 10:47:56 +01:00
d9570ec8d0 add imagepullpolicy rule 2023-12-11 10:47:56 +01:00
3dba6c0d69 set hydra-oidc side container 2023-12-11 10:47:56 +01:00
a56089efe5 Utilisation images symfony-containers 2023-12-11 10:47:56 +01:00
8075071f22 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-06-12 14:07:51 +02:00
2a479a1f86 feat: add hydra-oidc component 2023-02-01 14:02:39 +01:00