Stop mentioning LegacyNodeRoleBehavior for ServiceNodeExclusion labels#17542
Stop mentioning LegacyNodeRoleBehavior for ServiceNodeExclusion labels#17542k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
The text gives me an impression that LegacyNodeRoleBehavior somehow affects which label is in effect. But actually it doesn't.
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit 646ae78 https://deploy-preview-17542--kubernetes-io-master-staging.netlify.com |
|
Is this also a bug in Kubernetes itself? I wonder if the docs are only right until the code is fixed to have the intended behavior? |
|
/sig network |
|
I looked at https://github.com/kubernetes/kubernetes/blob/ace98e13820c267cbc4b3ddd8bebdc9a2fda7e4f/pkg/controller/service/controller.go and this PR seems to match what I saw. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubernetes#17542) The text gives me an impression that LegacyNodeRoleBehavior somehow affects which label is in effect. But actually it doesn't.
The text gives me an impression that LegacyNodeRoleBehavior somehow
affects which label is in effect. But actually it doesn't.