Canonical K8s based DSS exposes notebooks on public interfaces

[kenvandine]

With the microk8s based DSS the notebooks were only exposed on virtual private interfaces but with the transition to Canonical K8s they are now exposed on the public interface, which isn't acceptable by default for desktop/workstation usage.

[misohu]

Hi @kenvandine thanks for your issue. I am not sure if i understand the difference between microk8s and canonical k8s approach you mentioned. If I understand correctly the way how we create services for notebooks is the same for microk8s and caonnical k8s, its clusterIP and we just use the fact that those cluster IPs are accessible from host machine. So our approach did not change.

[kenvandine]

I haven't tested lately, but in my early testing of 1.1 from beta I was able to access those containers from the external IP address of my laptop. So I was able to connect to my notebooks from external computers. I'll re-test this to verify. It might have only been mlflow that was accessible.

[kenvandine]

Ah, it's not the DSS notebooks that are exposed, the cluster is exposed on the external IP. So from another computer on my same WiFi I can access it at https://:6443. With the microk8s based solution that port was only open on localhost.