Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with k8s.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/ #21688

Closed
AlexPSplunk opened this issue Jun 12, 2020 · 7 comments · Fixed by #25624
Assignees
Labels
language/en Issues or PRs related to English language

Comments

@AlexPSplunk
Copy link

This is a Bug Report

On the page: https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/#forward-a-local-port-to-a-port-on-the-pod
Under the section: Forward a local port to a port on the Pod
This page suggests using kubectl port-forward to forward ports to your pod. However, kubectl port-forward does not return, it is not daemonized by default. The page does not note this fact

Proposed Solution:
Either:

  • modify the page to indicate that kubectl port-forward will not return, and that the user needs to open another terminal window to continue with the exercises;
    OR
  • modify the kubectl port-forward commands to include a & (ampersand) at the end of the line, so that the job will run in the background and return to the terminal prompt.

Page to Update:
https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/

@tengqm
Copy link
Contributor

tengqm commented Jun 13, 2020

/language en

@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Jun 13, 2020
@Cweiping
Copy link

/assign

@Cweiping
Copy link

Maybe adding a flag to kubectl port-forward is a better way to solve this problem, such as docker run --detach?

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 14, 2020
@tengqm
Copy link
Contributor

tengqm commented Sep 14, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 14, 2020
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 13, 2020
@Cweiping
Copy link

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
language/en Issues or PRs related to English language
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants