-
Notifications
You must be signed in to change notification settings - Fork 50
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
1.7/edge bundle cannot be deployed due to the circular dependency #605
Comments
This change was introduced in canonical/oidc-gatekeeper-operator#78, however, it should not be in 1.7/edge rather latest/edge. @beliaev-maksim Is this deployed with 1.7/edge not latest? |
@beliaev-maksim I think you mentioned a check in the OIDC charm rewrite that you re--enabled and caused this problem, am I remembering correctly? Can you point to this in the code? |
It is both edges |
I see a manual release of the charm in main to 1.7/edge but if we want to update |
I was not able to reproduce this with the following channels: istio gateway is not waiting for istio pilot, status:
and the istio gateway service was created, I can get the IP with:
from my understanding of the istio charms, istio pilot should send the data to istio gateway, without waiting for the ingress-auth relation data from oidc. |
tested with latest/edge bundle, did not hit this issue. Closing as the bug is currently not in any of charmed kubeflow bundle's channels. |
running tests for bundle discovered a bug with circular dependency
https://github.com/canonical/bundle-kubeflow/actions/runs/5063062459/jobs/9102852996
istio gateway waits for istio pilot
but istio pilot waits for relation data from OIDC
but to configure OIDC I need istio gateway URL
but in order to set public URL on OIDC we might need to parse it from
istio-ingressgateway
The text was updated successfully, but these errors were encountered: