Ory hydra

[Bdegraaf1234]

Description of the change

Add ory-hydra as a component

Benefits

We can move away from managementportal as a resource server

Possible drawbacks

Applicable issues

Additional information

This is a stub/WIP

Checklist

• Make sure application versions in compatiblity section of README is same as the versions tested in CI

[yatharthranjan]

@pvannierop are there any plans on progressing this from the hyve?

[yatharthranjan]

@pvannierop never mind, I am starting work on this now. Thanks.

[yatharthranjan]

@mpgxvii can you please add the webhook jsonnet body and the updated identities please?

[mpgxvii]

@mpgxvii can you please add the webhook jsonnet body and the updated identities please?

Added the identities and added the webhook jsonnet to the configmap here: RADAR-base/radar-helm-charts#260.

[yatharthranjan]

LGTM, if someone else can review too, then I will proceed with the merge

[pvannierop]

LGTM!

[mpgxvii]

Waiting on this release: RADAR-base/radar-helm-charts#262, then will merge.

[keyvaann]

@mpgxvii I tried to update our instance with changes from this PR and I get these messages:

-> kubectl logs kratos-selfservice-ui-node-radar-self-enrolment-ui-7f948f7qh4j4                                

> @ory/[email protected] start
> next start -p 3000

npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /.npm
npm ERR! errno -13
npm ERR! 
npm ERR! Your cache folder contains root-owned files, due to a bug in
npm ERR! previous versions of npm which has since been addressed.
npm ERR! 
npm ERR! To permanently fix this problem, please run:
npm ERR!   sudo chown -R 10000:10000 "/.npm"

npm ERR! Log files were not written due to an error writing to the directory: /.npm/_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal

Also Helmfile sends this warning:

  W1007 19:14:41.326707 2290828 warnings.go:70] spec.template.spec.containers[0].env[10]: hides previous definition of "HYDRA_ADMIN_URL", which may be dropped when using apply

[mpgxvii]

Hi @keyvaann, this is fixed, but it wasn't merged to the dev branch which is the docker image used here. I have now merged this and the docker image is now published.

[keyvaann]

Hi @mpgxvii, how should I apply the fix?
I tried again to install the changes from the pr on our server and it failed again.

[mpgxvii]

Hi @mpgxvii, how should I apply the fix? I tried again to install the changes from the pr on our server and it failed again.

@keyvaann Oh the permission issue is now fixed but I think the healthcheck need to be temporarily disabled since those changes are not yet merged. I'll open a PR for the updated values.