Skip to content

🐛 enable managedAPIServerLoadBalancer w/ existing network #548

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

Merged

Conversation

gdetal
Copy link
Contributor

@gdetal gdetal commented Apr 21, 2020

What this PR does / why we need it:

Using managedAPIServerLoadBalancer: true in the OpenStackCluster configuration suggest that a load balancer will be created. However, when specifying an existing Openstack network instead of using nodeCidr, a load balancer is not created.

This PR make sure that:

  • the load balancer is created;
  • the controller do not try to remove the existing network.

Which issue(s) this PR fixes *
fixes #547

Special notes for your reviewer:

  • I had to refactor reconcileNormal as the linter was complaing about a cyclomatic complexity above 30 after my change.

Release note:


@k8s-ci-robot
Copy link
Contributor

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
  • If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
  • Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Apr 21, 2020
@k8s-ci-robot
Copy link
Contributor

Welcome @gdetal!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-openstack 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-openstack has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Hi @gdetal. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 21, 2020
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 21, 2020
@gdetal
Copy link
Contributor Author

gdetal commented Apr 21, 2020

/assign @luxas

@gdetal gdetal changed the title 🐛 enable managedAPIServerLoadBalancer w/ existing network 🐛 enable managedAPIServerLoadBalancer w/ existing network Apr 21, 2020
@theopenlab-ci
Copy link

theopenlab-ci bot commented Apr 21, 2020

Build failed.

@jichenjc
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot 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 Apr 22, 2020
@gdetal
Copy link
Contributor Author

gdetal commented Apr 22, 2020

/retest

@gdetal gdetal force-pushed the fix-managed-lb-existing-network branch from 23642f8 to 269505f Compare April 22, 2020 07:28
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 22, 2020
Copy link
Contributor

@flaper87 flaper87 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey folks, I don't work in this project anymore. Would you mind removing me from the reviewers list? Thanks

@gdetal
Copy link
Contributor Author

gdetal commented Apr 22, 2020

CLA check

@theopenlab-ci
Copy link

theopenlab-ci bot commented Apr 22, 2020

Build failed.

@sbueringer
Copy link
Member

Hey folks, I don't work in this project anymore. Would you mind removing me from the reviewers list? Thanks

@flaper87 Yup, no problem

Copy link
Member

@sbueringer sbueringer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just some nits

@sbueringer
Copy link
Member

@gdetal just fyi the openlab test has currently an open issue unrelated to your PR, but it's optional for merge (theopenlab/openlab#504)

@sbueringer
Copy link
Member

/assign

@gdetal gdetal force-pushed the fix-managed-lb-existing-network branch from 269505f to 7a40347 Compare April 23, 2020 05:54
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 23, 2020
@theopenlab-ci
Copy link

theopenlab-ci bot commented Apr 23, 2020

Build failed.

@sbueringer
Copy link
Member

sbueringer commented Apr 23, 2020

/approve
recheck

Edit: @gdetal looks good to me. Thx for the PR. Now you just have to fix the CLA issue :)

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gdetal, sbueringer

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 23, 2020
@sbueringer
Copy link
Member

/assign
@jichenjc can you also take a look please?

@jichenjc
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 24, 2020
@gdetal
Copy link
Contributor Author

gdetal commented Apr 24, 2020

Thanks for the review, I still have that CLA issue ongoing... I signed the document but still the bot didn't update the label... @k8s-ci-robot

@sbueringer
Copy link
Member

/check-cla

@sbueringer
Copy link
Member

Hm the recheck command should work (https://prow.k8s.io/plugins) Looks like something wrong with either your CLA or the CLA system / bot

@gdetal
Copy link
Contributor Author

gdetal commented Apr 24, 2020

@sbueringer that is what I thought, I'll create a ticket on the linuxfoundation support website.

@gdetal
Copy link
Contributor Author

gdetal commented Apr 24, 2020

/check-cla

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Apr 24, 2020
@k8s-ci-robot k8s-ci-robot merged commit b62656c into kubernetes-sigs:master Apr 24, 2020
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", 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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to use an existing network and managedAPIServerLoadBalancer: true
6 participants