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.

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

OCPBUGS-24044: Merge https://github.com/kubernetes/cloud-provider-gcp:master (522e293) into master #40

Merged

Conversation

cloud-team-rebase-bot[bot]
Copy link

No description provided.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 2, 2023
Copy link

openshift-ci bot commented Nov 2, 2023

Hi @cloud-team-rebase-bot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

panslava and others added 5 commits December 4, 2023 19:07
- After this commit repo will be unbuildable because of breaking changes
  in k8s-cloud-provider. Next commit will fix the build
- k8s-cloud-provider added "options ...cloud.Option" to every mock hook
  function signatures. This commit changes our mocks to have the same
  signature
- This commit fixes repo build
Update k8s-cloud-provider version
@cloud-team-rebase-bot cloud-team-rebase-bot bot changed the title Merge https://github.com/kubernetes/cloud-provider-gcp:master (992c1c3) into master Merge https://github.com/kubernetes/cloud-provider-gcp:master (522e293) into master Dec 7, 2023
@cloud-team-bot cloud-team-bot bot force-pushed the rebase-bot-master branch 2 times, most recently from 9eb6555 to 83e5c61 Compare December 11, 2023 12:47
cloud-team-rebase-bot and others added 4 commits December 14, 2023 12:44
97e991b drops `maxNodeNamesToLog` when
applied on top of 0ee532a

Signed-off-by: Nolan Brubaker <nolan@nbrubaker.com>
JoelSpeed and others added 5 commits December 14, 2023 12:45
Based on docs for internal loadbalancer here [1], backend services [2]
and instances in instance-groups [3], following restrictions apply:

- Internal LB can load balance to VMs in same region, but different
  subnets
- Instance groups for the backend service must contain instance of
  the same subnet
- An instance can only belong to one load balanced instance group
- It is probably useful use-case to have nodes for the cluster belong
  to more than one subnet. And the current setup fails to create an
  internal load balancer with nodes in multiple subnets.

This change finds pre-existing instance-groups that ONLY contain
instances that belong to the cluster, uses them for the backend
service. And only ensures instance-groups for remaining ones.

[1] https://cloud.google.com/load-balancing/docs/internal
[2] https://cloud.google.com/load-balancing/docs/backend-service#restrictions_and_guidance
[3] https://cloud.google.com/compute/docs/instance-groups/creating-groups-of-unmanaged-instances#addinstances

Co-authored-by: Abhinav Dahiya <abhinav.dahiya@redhat.com>
Signed-off-by: Nolan Brubaker <nolan@nbrubaker.com>

# Conflicts:
#	vendor/k8s.io/cloud-provider-gcp/providers/gce/gce.go
#	vendor/k8s.io/cloud-provider-gcp/providers/gce/gce_fake.go
#	vendor/k8s.io/cloud-provider-gcp/providers/gce/gce_instancegroup.go
#	vendor/k8s.io/cloud-provider-gcp/providers/gce/gce_loadbalancer_internal.go
@JoelSpeed
Copy link

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 18, 2023
@JoelSpeed JoelSpeed changed the title Merge https://github.com/kubernetes/cloud-provider-gcp:master (522e293) into master OCPBUGS-24044: Merge https://github.com/kubernetes/cloud-provider-gcp:master (522e293) into master Dec 18, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 18, 2023
@openshift-ci-robot
Copy link

@cloud-team-rebase-bot[bot]: This pull request references Jira Issue OCPBUGS-24044, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

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.

@JoelSpeed
Copy link

/approve
/lgtm

Just manually tested this and it resolves an issue we have been having with internal to external migration

/cherry-pick release-4.15

@openshift-cherrypick-robot

@JoelSpeed: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

In response to this:

/approve
/lgtm

Just manually tested this and it resolves an issue we have been having with internal to external migration

/cherry-pick release-4.15

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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 18, 2023
Copy link

openshift-ci bot commented Dec 18, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 18, 2023
@openshift-merge-bot openshift-merge-bot bot merged commit 6ad9e62 into openshift:master Dec 18, 2023
4 of 6 checks passed
@openshift-ci-robot
Copy link

@cloud-team-rebase-bot[bot]: Jira Issue OCPBUGS-24044: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-24044 has been moved to the MODIFIED state.

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.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-gcp-cloud-controller-manager-container-v4.16.0-202312181310.p0.g6ad9e62.assembly.stream for distgit ose-gcp-cloud-controller-manager.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet