KusionStack / KusionStack/kusion
Feat: optimize port forwarding for kusion apply
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 108
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
### What would you like to be added?
Please optimize the `--port-forwarding` flag for `kusion apply` command:
- Support direct port forwarding to **Pod** instead of relying on K8s **Service**
- Support customized the local forwarding port number
### Why is this needed?
Current, the `--port-forward` flag only supports applications with K8s **Service** resources, and the local forwarding port number needs to be consistent with that of the Service, which may easily lead to conflicts.
Contributor guide
Research direction
Start by tracing how the kusion apply command handles the --port-forwarding flag and how it currently selects a Kubernetes Service and local port. Reproduce the existing behavior, then identify the Pod-forwarding and local-port paths that need to support the two requested cases; done means forwarding works directly to a Pod and accepts a customized local port without Service-port conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100