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.

Sign up for GitHub

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

Jump to bottom

ServiceNodePortStaticSubrange not mentioned in virtual IPs page #40562

Open
sftim opened this issue Apr 8, 2023 · 7 comments
Open

ServiceNodePortStaticSubrange not mentioned in virtual IPs page #40562

sftim opened this issue Apr 8, 2023 · 7 comments
Assignees
@KhushPatibandha
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sftim
Copy link
Contributor

sftim commented Apr 8, 2023

This is a Bug Report

Problem:
ServiceNodePortStaticSubrange is not mentioned in the Virtual IPs and Service Proxies page, not even for the v1.27 docs.

Proposed Solution:
Update Virtual IPs and Service Proxies to mention subranges for NodePort allocation types. It should, because it is misleading for the Avoiding collisions heading not to mention the (now) two mechanisms that Kubernetes offers for this.

Page to Update:
https://deploy-preview-39124--kubernetes-io-main-staging.netlify.app/docs/reference/networking/virtual-ips/#avoiding-collisions

Additional Information:
/sig network

Relevant to #39850
@sftim sftim added the kind/bug Categorizes issue or PR as related to a bug. label Apr 8, 2023
@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 8, 2023
@KhushPatibandha
Copy link
Contributor

Hey, I would like to work on this.
/assign

@KhushPatibandha KhushPatibandha mentioned this issue Apr 10, 2023
Closed
@KhushPatibandha
Copy link
Contributor

@sftim I have opened a PR for this issue and tried to resolve it as per my knowledge, do let me know if you have some feedback that could help.

@KhushPatibandha KhushPatibandha mentioned this issue Apr 12, 2023
Closed
@k8s-triage-robot
Copy link

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/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 Jul 9, 2023
@vaibhav2107
Copy link
Member

/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 Aug 7, 2023
@vaibhav2107
Copy link
Member

@KhushPatibandha Are you still working on this issue?

@k8s-triage-robot
Copy link

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/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 Mar 12, 2024
@natalisucks
Copy link
Contributor

/remove-lifecycle stale
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KhushPatibandha KhushPatibandha

Labels
kind/bug Categorizes issue or PR as related to a bug. sig/network Categorizes an issue or PR as relevant to SIG Network. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[WIP] explain static subrange for NodePort KhushPatibandha/k8s-website
6 participants
@natalisucks @k8s-ci-robot @sftim @k8s-triage-robot @vaibhav2107 @KhushPatibandha