kubernetes / website

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

Describe health check node ports in Service concept #38329

Open sftim opened 1 year ago

sftim commented 1 year ago

This is a Feature Request

What would you like to be added Add a good explanation for why Kubernetes has health check node ports (ie, to support integration with cloud load balancers), as well as when you'd want this assigned automatically, and when you'd want to define one.

The page to update is https://k8s.io/docs/concepts/services-networking/service/; it's OK to update other pages at the same time, such as https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/

Why is this needed Kubernetes Services have a healthCheckNodePort field in their spec, but as a project we don't really explain what this is.

Comments The diagram in https://k8s.io/blog/2022/12/30/advancements-in-kubernetes-traffic-engineering/ (due out later this month) should help people who are documenting this. If you're not sure how this works but want to document it, it's OK to wait to read that article once it's published.

/language en /sig network.

k8s-ci-robot commented 1 year ago

@sftim: The label(s) sig/network. cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/website/issues/38329): >**This is a Feature Request** > > > > >**What would you like to be added** >Add a good explanation for _why_ Kubernetes has health check node ports (ie, to support integration with cloud load balancers), as well as when you'd want this assigned automatically, and when you'd want to define one. > >The page to update is https://k8s.io/docs/concepts/services-networking/service/; it's OK to update other pages at the same time, such as https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/ > >**Why is this needed** >Kubernetes Services have a `healthCheckNodePort` field in their `spec`, but as a project we don't really explain what this is. > >**Comments** >The diagram in https://k8s.io/blog/2022/12/30/advancements-in-kubernetes-traffic-engineering/ (due out later this month) should help people who are documenting this. If you're not sure how this works but want to document it, it's OK to wait to read that article once it's published. > >/language en >/sig network. 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.
Pradumnasaraf commented 1 year ago

/triage accepted

kundan2707 commented 1 year ago

/sig network

k8s-triage-robot commented 9 months ago

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

k8s-triage-robot commented 6 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 5 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 4 months 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 4 months ago

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

In response to [this](https://github.com/kubernetes/website/issues/38329#issuecomment-2174417644): >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.
kundan2707 commented 4 months ago

/reopen

k8s-ci-robot commented 4 months ago

@kundan2707: Reopened this issue.

In response to [this](https://github.com/kubernetes/website/issues/38329#issuecomment-2176589876): >/reopen 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.
kundan2707 commented 4 months ago

/remove-lifecycle rotten

kundan2707 commented 3 months ago

/assign

k8s-triage-robot commented 3 weeks 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