search

kubernetes / website

Kubernetes website and documentation repo:
https://kubernetes.io
Creative Commons Attribution 4.0 International
4.36k stars 14.12k forks source link

Add example for proxying to pods in “Manually constructing apiserver proxy URLs” section #41621

Closed jiec-msft closed 1 month ago

jiec-msft commented 1 year ago

In manually-constructing-apiserver-proxy-urls, can we add example for proxy to pods? For example:

http://kubernetes_master_address/api/v1/namespaces/namespace_name/services/[http:]podName[:port_name]/proxy

k8s-ci-robot commented 1 year ago

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
dipesh-rawat commented 1 year ago

Page related to issue: https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster-services/ /language en

dipesh-rawat commented 1 year ago

/retitle Add example for proxying to pods in Manually constructing apiserver proxy URLs section

sftim commented 1 year ago

/retitle Add example for proxying to pods in “Manually constructing apiserver proxy URLs” section

sftim commented 1 year ago

https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster-services/#manually-constructing-apiserver-proxy-urls is quite out of date. It will be more valuable to update the existing page than to make the change you're suggesting here @jiec-msft

If we have capacity to do both things: great!

jiec-msft commented 1 year ago

https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster-services/#manually-constructing-apiserver-proxy-urls is quite out of date. It will be more valuable to update the existing page than to make the change you're suggesting here @jiec-msft

If we have capacity to do both things: great!

@sftim Great to know this. lol

jiec-msft commented 12 months ago

@sftim May I tentatively ask about the update?

sftim commented 11 months ago

Hi @jiec-msft

If your question is similar to “has anyone contributed work towards this issue, so far?” then, in my judgement, nobody has.

jiec-msft commented 11 months ago

@sftim Got it, thanks!

jiec-msft commented 6 months ago

Hey @sftim, may I ask if there is any update?

sftim commented 6 months ago

Hey @sftim, may I ask if there is any update?

If your question is similar to “has anyone contributed work towards this issue, so far?” then, in my judgement, nobody has.

(Kubernetes contributors are mainly volunteers - although if you'd like to pay someone to do the work, there are companies that would be willing to help).

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 month ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/website/issues/41621#issuecomment-2144850859): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.