-
Notifications
You must be signed in to change notification settings - Fork 17
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
[WIP] OCPBUGS-7359: Azure: move to kube-proxy LB probes, don't detach masters when unready #60
[WIP] OCPBUGS-7359: Azure: move to kube-proxy LB probes, don't detach masters when unready #60
Conversation
@damdo: This pull request references Jira Issue OCPBUGS-7359, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
bb5a9a7
to
04f8b7e
Compare
@damdo: This pull request references Jira Issue OCPBUGS-7359, which is invalid:
Comment 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would like to see some unit testing to make sure we are getting the expected ports and health paths out of this before we merge
@@ -2198,7 +2206,7 @@ func (az *Cloud) buildHealthProbeRulesForPort(serviceManifest *v1.Service, port | |||
} | |||
} | |||
if path == nil { | |||
path = pointer.String(consts.HealthProbeDefaultRequestPath) | |||
path = pointer.String("/healthz") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the default request path? Is it not already /healthz
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No the default is /
Do we want to change that at the const level?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where else is the const used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nowhere else. So we can probably change it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then I would change it yes :)
@@ -2178,7 +2186,7 @@ func (az *Cloud) buildHealthProbeRulesForPort(serviceManifest *v1.Service, port | |||
//nolint:gosec | |||
if item.Port == int32(port) { | |||
//found the port | |||
properties.Port = pointer.Int32(item.NodePort) | |||
properties.Port = pointer.Int32(lbNodesHealthCheckPort) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this correct? Is this not someone having specified in an annotation that they want a specific port? I'm not sure why there seems to be an override here anyway? Can you explain why this needs to be changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah wanted to ask you an opinion on this.
Not sure why the probe port is being overridden by the NodePort here.
But if that's because we are "defaulting" then I think we should set it to lbNodesHealthCheckPort
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would need to dig into the code to work out and have an opinion on this, have you done any archeology to work out when this was introduced and why?
@damdo: The following tests failed, say
Full PR test history. Your PR dashboard. 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 understand the commands that are listed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This commit will want to be UPSTREAM: XXXX:
so that once we agree on the approach upstream we can drop this, need a PR for that though
PR needs rebase. 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. |
/close We've superseded this now |
@damdo: This pull request references Jira Issue OCPBUGS-7359. The bug has been updated to no longer refer to the pull request using the external bug tracker. 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. |
@JoelSpeed: Closed this PR. 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. |
CCM change matching in-tree: openshift/kubernetes#1506
TODO: