-
Notifications
You must be signed in to change notification settings - Fork 195
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
Take the lastest changes from upstream kuberneres gce provider code #422
Conversation
/hold |
/assign @jprzychodzen |
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-contributor-experience at kubernetes/community. /check-cla |
…staging/src/k8s.io/legacy-cloud-providers/gce) commit id 68f808e6db388b249dae8c6c9dfb078bc0947b49
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cezarygerard 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 |
@@ -51,6 +53,11 @@ const ( | |||
// new load balancers and updating existing load balancers, recognizing when | |||
// each is needed. | |||
func (g *Cloud) ensureExternalLoadBalancer(clusterName string, clusterID string, apiService *v1.Service, existingFwdRule *compute.ForwardingRule, nodes []*v1.Node) (*v1.LoadBalancerStatus, error) { | |||
// Skip service handling if it uses Regional Backend Services and handled by other controllers | |||
if usesL4RBS(apiService, existingFwdRule) { |
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 concerning?
in which versions is this controller running?
does it conflict with L4RBS implementation?
@cezarygerard: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
/assign @sdmodi |
@cezarygerard: GitHub didn't allow me to assign the following users: sdmodi. 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. |
|
||
destinationRanges := []string{ipAddress} | ||
|
||
if !reflect.DeepEqual(destinationRanges, fw.DestinationRanges) { |
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 comparison is a bit awkward since destination ranges only has an IP address, no?
if len(fw.DestinationRanges) == 1 && fw.DestinationRanges[0] == ipAddress
since this seems to be pulled from intree we can follow up later
I am not able to rerun the tests locally, and I will probably need to use the debugger. Also I don't understand full why CCM has diverged form KCM in a way that KCM had some code added (by me and Slavik) and the CCM had some code added? What was the purpose of the new code in the CCM? It had never run on production. |
/assign @bowei if the controllers drift it may cause problems on upgrades, |
As per why specific changes were not picked up by |
/test cloud-provider-gcp-verify-up-to-date |
@@ -492,7 +520,7 @@ func TestUpdateInternalLoadBalancerNodes(t *testing.T) { | |||
assert.Contains( | |||
t, | |||
instances[0].Instance, | |||
fmt.Sprintf("%s/zones/%s/instances/%s", vals.ProjectID, vals.ZoneName, node2Name), | |||
fmt.Sprintf("projects/%s/zones/%s/instances/%s", vals.ProjectID, vals.ZoneName, node2Name), |
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.
Please don't change that. legacy-cloud-provider
has too old version of the /api library, which has different behavior for listing instances.
This was fixed in #262 for cloud-provider-gcp repository.
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. |
This PR (with fixes) already happened. See #466 |
/close |
@jprzychodzen: 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. |
Take the lastest changes from upstream kuberneres gce provider code (staging/src/k8s.io/legacy-cloud-providers/gce)
upstream commit id 68f808e6db388b249dae8c6c9dfb078bc0947b49