Local Install: Explicit Port Forwarding for Frontend needed

Help! Browsertrix
1

Following Local Deployment - Browsertrix Docs, we set up a local install on Docker Desktop on Windows. For http://localhost:30870/ to work, we always need do run kubectl port-forward svc/browsertrix-cloud-frontend 30870:80 in a parallel console despite the fact that local_service_port: 30870 seems to be set correctly.

Today we did a quite different local install on Arch Linux using Minikube, where the exact same workaround is needed. So this no longer looks like a flaw of Docker Desktop’s builtin Kubernetes…

Any idea to avoid this workaround and have port 30870 working instantly?

2

Which version of Docker Desktop are you using?
What is the output when you run kubectl get svc browsertrix-cloud-frontend?

Minikube has always required port forwarding, as we explain in the note on: Local Deployment - Browsertrix Docs

Edit: the note is for MacOS, it’s likely that it applies to other platforms. We haven’t had time to test Minikube recently.

But we do use local_service_port on MacOS fairly regularly, and I imagine the Windows K8s for Docker Desktop is similar

3

<windows>

4.78.0

NAME                         TYPE       CLUSTER-IP    EXTERNAL-IP   PORT(S)        AGE
browsertrix-cloud-frontend   NodePort   10.96.5.198   <none>        80:30870/TCP   37d

</windows>

<linux>

In contrast to MacOS, Minikube on Arch does serve port 30870, but on an unexpected IP:

$ minikube service browsertrix-cloud-frontend --url
http://192.168.49.2:30870

</linux>

This one is directly useable on the host, thanks for the pointer!
Heinz