Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconciler is not using Hydra admin url from spec #82

Closed
athak opened this issue Aug 26, 2021 · 3 comments
Closed

Reconciler is not using Hydra admin url from spec #82

athak opened this issue Aug 26, 2021 · 3 comments
Labels
bug Something is not working.

Comments

@athak
Copy link

athak commented Aug 26, 2021

Describe the bug

We want to deploy multiple Hydra instances and use a single maester instance. The maester instance is in namespace A and the Hydra instances and OAuth2Client definitions are on namespace B.

All OAuth2Client definitions are specifying a hydraAdmin block to point to the corresponding Hydra instance admin. The maester however seems to ignore the override and uses the default admin URL.

To Reproduce

Steps to reproduce the behavior:

  • Deploy a single instance of the hydra-maester Helm chart in namespace A
  • Deploy one or more instances of Hydra using the hydra Helm chart (with maester.enabled set to false) in namespace B
  • Deploy one or more OAuth2Client definitions specifying the hydraAdmin block in the spec to point to the deployed Hydra instance services.

Expected behavior

The maester should use the URL from the hydraAdmin block of the OAuth2Client definition and should register the client with Hydra admin instance successfully.

Environment

  • Version 0.19.3 of both Helm charts
  • GKE, v1.20.8-gke.900
@piotrmsc
Copy link
Collaborator

piotrmsc commented Aug 31, 2021

Hello @athak, thanks for reporting that! I have reproduced the issue and can confirm it. Without yet checking the linked PR I have also checked and believethis commit produced the issue and regression.
I will review the PR and once fix is done will let you know ;-)
Side note to me and @Demonsthere clearly we lack test for this flow :P Otherwise, it would pop up on earlier :D

@Demonsthere
Copy link
Collaborator

The linked PR has been merged, can this be closed?

@piotrmsc
Copy link
Collaborator

yes, it was also released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working.
Projects
None yet
Development

No branches or pull requests

3 participants