-
Notifications
You must be signed in to change notification settings - Fork 39
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
allow customising currently hard-coded service hostnames #457
Closed
Comments
tiborsimko
added a commit
to tiborsimko/reana-commons
that referenced
this issue
May 6, 2024
Remove hard-coded infrastructure component host name domain "svc.local.cluster", since this assumption is not really necessary and made REANA not to work under some deployment scenarios, such as on SSL-RIVER. Closes reanahub#457
tiborsimko
added a commit
to tiborsimko/reana-commons
that referenced
this issue
May 6, 2024
Remove hard-coded infrastructure component host name domain "svc.local.cluster", since this assumption is not really necessary and made REANA not to work under some deployment scenarios, such as on SSL-RIVER. Closes reanahub#457
tiborsimko
added a commit
to tiborsimko/reana-commons
that referenced
this issue
May 6, 2024
Removes hard-coded infrastructure component host name domain "svc.local.cluster", since this assumption is not really necessary and made REANA not to work under some deployment scenarios, such as on SSL-RIVER. Closes reanahub#457
tiborsimko
added a commit
to tiborsimko/reana-server
that referenced
this issue
May 15, 2024
…ahub#687) Removes hard-coded infrastructure component host name domain "svc.local.cluster" during interactive session clean-up procedures, since this assumption is not really necessary and would not work under some deployment scenarios, such as on SSL-RIVER. Closes reanahub/reana-commons#457
This was
linked to
pull requests
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have currently hard-coded component hostnames in
config.py
:This causes troubles for the RIVER-SSL deployment due to using different domain.
(See also the ClusterRole to Role tentative changes here: https://github.com/reanahub/reana/pull/291/files that may or may not be needed.)
Basically, instead of always appending
svc.cluster.local
, we could make this part customisable via Helm values.Note that the reana-server component is also concerned:
The text was updated successfully, but these errors were encountered: