You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if the helm chart would provide the option to inject an init container which waits until the oidc discovery endpoint is up and running.
Otherwise, harbor might start and if the oidc discovery endpoint is temporary not available, harbor will disable the OIDC login button. The discovery is also not retried by the harbor core. This is highly confusing as one would expect better resiliency during harbor startup.
This issue could be solved either in the harbor core or in the helm chart I guess.
The text was updated successfully, but these errors were encountered:
It would be nice if the helm chart would provide the option to inject an init container which waits until the oidc discovery endpoint is up and running.
Otherwise, harbor might start and if the oidc discovery endpoint is temporary not available, harbor will disable the OIDC login button. The discovery is also not retried by the harbor core. This is highly confusing as one would expect better resiliency during harbor startup.
This issue could be solved either in the harbor core or in the helm chart I guess.
The text was updated successfully, but these errors were encountered: