minikube tunnel should have background mode

[ctcampbell]

It would be useful if Minikube tunnel had a background/daemon mode. It would also be nice if it could be started whenever Minikube starts without having to do anything.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[ajit555db]

minikube tunnel &> /dev/null &

[tstromberg]

I don't know that we need to reinvent our own shell backgrounding process, but perhaps it would be nice to incorporate something so that minikube start --tunnel could work.

This is also related to some UI ideas we've had.

[priyawadhwa]

If anybody is interested in implementing minikube start --tunnel, please feel free to assign yourself to this issue by commenting /assign.

[medyagh]

this issue is still open for anyone interested to do this.

[ghost]

@medyagh Far from being an expert on Go but I think this might be a start #8266

[medyagh]

I would accept any PR that adds this feature

[m-lima]

minikube tunnel &> /dev/null &

In general, I don't like this solution because it simply redirects the stdout and stderr and detaches the process; closing the session would still kill the tunnel. Not actually a solution for what OP wanted.
But that's besides the point I'm here to comment about: it seems like when you kill minikube tunnel with a kill -INT the ssh forwards survive the death of the parent process. The signal is captured by cmd/minikube/cmd/tunnel.go, but the ssh sessions persist.
I noticed this happening as late as 18e215fed113d3ad1bc1797860e303cae0772373

[gtmanfred]

I would also love this feature.

[AviMoto]

+1 to this feature

[codingluke]

👍 for this feature!

[warent]

yes please! don't let this go stale

[hongliang5316]

+1

[gautambaghel]

+1

[Merteg]

/assign
I need this and I think I know something about Go )

[renato-r-cardoso-alb]

/assign

[warent]

FYI for anyone wondering I found a way to accomplish something similar and more permanently using loadbalancers.

First, you want to get the IP address to the cluster using minikube profile list, and then plug that into your k8s service using the externalIPs property, like so:

---
apiVersion: v1
kind: Service
metadata:
  name: frontend
  namespace: default
spec:
  type: LoadBalancer
  selector:
    frontend: web
  ports:
    - protocol: "TCP"
      # Port accessible inside cluster
      port: 3000
      # Port to forward to inside the pod
      targetPort: 3000
      # Port accessible outside cluster
      nodePort: 31000
  externalIPs:
    - 192.168.94.2

This will allow you to access your service in the host machine: 192.168.94.2:31000

[surajkrishan]

much needed feature

[MrEyratnz]

I would love to see this feature added

• run in the background
• option on minikube start to start the tunnel automatically

[shanginn]

I would love to see that feature too.

but for now I'm just starting the tunnel inside a screen

maybe slightly better than &> /dev/null & ¯_(ツ)_/¯

[entrymon]

I would love this feature too, earlier minikube tunnel use to remain forever but now it cleans up automatically and --cleanup=false also does not work

[AndrewEastwood]

+1 to this

[dgoldssfo]

+1

Since all of us with ARM-based Macs use minikube tunnel now, maybe that gives this request a little higher priority than when the issue was first logged 4 years ago.

[lukasholzer]

+1 super painful currently

[szsascha]

+1

[itAvgur]

+1
I really need this feature for every day using

[odi89]

+1
Appreaciate the effort of this project=)

[sam-fiddis-rozettatech]

+1

[AdminMavericka]

+1

[freeyob]

+1

[ktn1234]

+1

[specialkapa]

+1

[callyourai]

+1

[ekneg54]

+1

[seanxue]

+1