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

Session with K8S helm install #6

Open
SpontaneousDuck opened this issue Dec 16, 2021 · 1 comment
Open

Session with K8S helm install #6

SpontaneousDuck opened this issue Dec 16, 2021 · 1 comment

Comments

@SpontaneousDuck
Copy link

Hello,

I just went through and installed clearml-server with the helm charts on our on-prem k8s cluster. It appears like this uses the persistent agent option instead of the glue option (link). Is it possible to use clearml-session with this setup? If so, how do I need to configure the session? Will I need to add a service to route the ssh connection through or is it being routed through an existing service?

Thanks for the help!

@jkhenning
Copy link
Member

Hi @SpontaneousDuck,

The clearml-session basically depends on an agent running the interactive session. However, assuming the interactive session will be spun up in a k8s pod, you'll need (as you mentioned), a pre-configured ingress to route the SSH connection. The k8s glue contains a mode called the "ports mode" which basically automatically labels pods spun up by the k8s glue (which acts as a daemon agent), allowing you to pre-configure a fixed ingress for such-labeled pods.
This will not be possible using the default "persistent agent" (as you've called it) which is an optional part of the Helm chart.

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

No branches or pull requests

2 participants