Open sftim opened 1 year ago
@sftim: The label(s) sig/network.
cannot be applied, because the repository doesn't have them.
/triage accepted
/sig network
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted
(org members only)/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
/reopen
@kundan2707: Reopened this issue.
/remove-lifecycle rotten
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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 theirspec
, 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.