-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Move Port out of node object #7891
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
@rmsilva1973: GitHub didn't allow me to assign the following users: me. Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I began taking a stab at this one. Soon will commit (to my fork) a proposed change so people can collaborate/help/criticize. 😊 |
/assign rmsilva1973 |
The Port attribute only applies to the API server, and therefore is a cluster-level attribute, rather than a node-level one, which currently causes nothing but confusing. Moving it out is the correct move here.
The text was updated successfully, but these errors were encountered: