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

CORS-3195: Azure CAPI Supplemental Load Balancers #8115

Merged
merged 3 commits into from
Apr 3, 2024

Conversation

patrickdillon
Copy link
Contributor

@patrickdillon patrickdillon commented Mar 6, 2024

Adds support for creating an additional, external LB. As well as updating the capi-provisioned internal LB with config for the machine-config server.

/cc @rna-afk @jhixson74

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 6, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 6, 2024

@patrickdillon: This pull request references CORS-3195 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

Adds support for creating an additional, external LB. As well as updating the capi-provisioned internal LB with config for the machine-config server.

/cc @rna-afk @jhixson74

Still need to update VM membership to join the backend pool.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from jhixson74 and rna-afk March 6, 2024 21:45
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 6, 2024
Copy link
Contributor

openshift-ci bot commented Mar 6, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@patrickdillon patrickdillon marked this pull request as ready for review March 28, 2024 22:39
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 28, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 28, 2024

@patrickdillon: This pull request references CORS-3195 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

Adds support for creating an additional, external LB. As well as updating the capi-provisioned internal LB with config for the machine-config server.

/cc @rna-afk @jhixson74

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 28, 2024
@patrickdillon patrickdillon force-pushed the azure-capi-lb branch 2 times, most recently from 1b45d58 to 18c3c1c Compare March 28, 2024 23:13
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 28, 2024
@patrickdillon patrickdillon force-pushed the azure-capi-lb branch 2 times, most recently from d610182 to 3d5d101 Compare March 29, 2024 02:24
@jhixson74
Copy link
Member

There are some gofmt and golint errors. Other than that, everything LGTM.

@jhixson74
Copy link
Member

/approve

Copy link
Contributor

openshift-ci bot commented Mar 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhixson74

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 Mar 29, 2024
@patrickdillon patrickdillon force-pushed the azure-capi-lb branch 3 times, most recently from 2d34945 to 7f2b833 Compare March 29, 2024 23:35
@patrickdillon
Copy link
Contributor Author

patrickdillon commented Mar 29, 2024

Adding a ControlPlaneOutboundLB to allow outbound access to the bootstrap node:

+                               ControlPlaneOutboundLB: &capz.LoadBalancerSpec{
+                                       FrontendIPsCount: to.Ptr(int32(1)),
+                               },

and adding the bootstrap ignition commits, this enables control plane nodes to pull ignition

Note that adding this precludes you from adding a public ip to the VM (a vm with a public ip config cannot have an outbound rule).

@jhixson74
Copy link
Member

/retest

@patrickdillon patrickdillon force-pushed the azure-capi-lb branch 2 times, most recently from a79084b to ea75eba Compare April 2, 2024 10:26
As part of the cluster-api-based Azure installation flow this
configures the CAPZ-created internal load balancer to serve
ignition to control plane machines. It also creates an external load
balancer when the cluster is public.
Adds armnetwork packages, for working with load balancers.
@patrickdillon
Copy link
Contributor Author

/retest

@jhixson74 I think the linting issues are fixed

@patrickdillon
Copy link
Contributor Author

/retest

Copy link
Contributor

openshift-ci bot commented Apr 2, 2024

@patrickdillon: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-e2e-aws-ovn-upgrade 1eb9d4f link false /test okd-e2e-aws-ovn-upgrade
ci/prow/e2e-azurestack 1eb9d4f link false /test e2e-azurestack

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.

@jhixson74
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 3, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit ac3ac89 into openshift:master Apr 3, 2024
24 of 26 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-installer-altinfra-container-v4.16.0-202404031748.p0.gac3ac89.assembly.stream.el8 for distgit ose-installer-altinfra.
All builds following this will include this PR.

@nrb
Copy link

nrb commented Apr 19, 2024

Created kubernetes-sigs/cluster-api-provider-azure#4755 to track implementing dual load balancer/endpoint logic upstream (a 4.17 concern), as well as creating OCPCLOUD-2588

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants