Open liu-hm19 opened 4 months ago
If --port-forward
flag needs to directly support the port forwarding of a Pod
, users seems to need to specify the name of the Pod
, unless the application resources contain only one Pod
. Since the Spec
does not include the labels
/annotations
to specify which Pod
corresponds to the Workload
, Kusion currently cannot recognize the Pod
for port forwarding. Thus, I think we may need to first implement adding labels
or annotations
for the Pods
corresponding to the Workload
. cc @SparkYuan
What would you like to be added?
Please optimize the
--port-forwarding
flag forkusion apply
command: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.