docs on how to set up Tilt port-forwarding with Traefik
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
In the #tilt channel, Meerkat asks:
I'm using tilt on a cluster that already has Traefik deployed on it, as in tilt has no knowledge of traefik while running.
But I need to do the tilt equivalent of this command:
kubectl port-forward --namespace traefik $(kubectl get pods --namespace traefik --selector "app.kubernetes.io/name=traefik" --output=name) 8000:8000
Currently, Tilt's port-forwarding logic isn't customizable enough to support something like this, since Tilt doesn't even watch pods that it doesn't deploy.
You can wire this together with
local_resource(serve_cmd=[shell script here])
to run the port-forwarder as a "local server"
I'm not totally sure what the right answer is here, though Traefik is becoming popular enough that we should have documentation on the recommended solution for something like this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the issue's kubectl port-forward command and the local_resource(serve_cmd=[shell script here]) example, then review how Tilt handles port-forwarding for resources it does deploy. Document the recommended way to connect Tilt to an externally managed Traefik instance, including what a working port-forward setup should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100