-
Notifications
You must be signed in to change notification settings - Fork 7
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
Yan 893 - Multinode deployments of helm charts (in-progress) #116
Conversation
Means there will only be a single daliuge-daemon pod deployed on each node. This minimises namespace conflicts.
Now, all requests to the exposed service hangs. This needs debugging.
Makes ip finding deterministic.
Removes needless printing from helm_client.
…T end-point. This code should not have to change much, although what it points to, will.
…e rather than fail on exception
… (requires both translator and engine).
# Conflicts: # daliuge-translator/dlg/dropmake/web/main.js # daliuge-translator/dlg/dropmake/web/pg_viewer.html
This feature is now relatively stable, supports multiple node (pod) deployments and is integrated with the latest master.
I argue that the implementation of the base feature is 'complete', however, there is still more that could be done. |
To replicate the entire stack locally: Setup K8s: Setup dlg-ood (3bff037) Setup lgweb (9e7d82c) One should be able to launch jobs through the helm deploy button in the translator view. |
Yan 893 - Multinode deployments of helm charts
Yan 893 - Multinode deployments of helm charts
An in-progress pull that permits single-node helm deployments from the translator interface (assuming the machine running the lg-web has access to kubectl).