Skip to content

Kubernetes: pods/portforward useful mode + real-runtime workloads (--run-workloads) #892

Description

@NitinKumar004

Deferred from #877/#408. pods/portforward currently returns 501 (exec/attach now work over WebSocket via #408). A useful port-forward needs an in-process pod:port handler registry (nothing listens on the pod port today), and real workload execution needs a runtime — both belong to the real-engine program. Also deferred: SPDY-over-WebSocket tunneling (kubectl v1.35 default for portforward), probe/metric actuation. Fix locus: services/kubernetes/pod.go (writeStreamingUnsupported), a pod:port handler seam.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions