-
Notifications
You must be signed in to change notification settings - Fork 216
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
MGMT-18913: Add support for external load balancer #6865
MGMT-18913: Add support for external load balancer #6865
Conversation
@jhernand: This pull request references MGMT-18913 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 epic to target the "4.18.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jhernand 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 |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6865 +/- ##
==========================================
+ Coverage 68.19% 68.67% +0.48%
==========================================
Files 279 249 -30
Lines 39282 37459 -1823
==========================================
- Hits 26788 25725 -1063
+ Misses 10061 9432 -629
+ Partials 2433 2302 -131
|
867aafa
to
49ae18e
Compare
This patch adds support for using an external load balancer. It will only be available for OpenShift 4.16 or newer. To enable it the user will have to use the new `load_balancer.type` field of the `cluster` type, for example: ```json { ... "load_balancer": { "type": "user-managed" } } ``` To preserve backwards compatibility this will be optional, and the default value will be `cluster-managed`. When the value is `user-managed` the following will be added to the generated `install-config.yaml` file: ```yaml platform: baremetal: loadBalancer: type: UserManaged ``` Or for _vSphere_: ``` platform: vsphere: loadBalancer: type: UserManaged ``` The database will be automatically migrated so that for existing clusters the value of the `load_balancer_type` column will automatically be set to `cluster-managed`. This patch adds this support only for the `baremetal` and `vsphere` platforms. Note that when using an external load balancer the VIPs will not be used, but we are still requiring them, and using them to calculate the machine CIDR. Insted we should validate that no VIPs are given, and we should calculate the machine CIDR in some other way. That is not part of this patch. Related: https://issues.redhat.com/browse/MGMT-18913 Signed-off-by: Juan Hernandez <[email protected]>
49ae18e
to
4664d6e
Compare
@jhernand: This pull request references MGMT-18913 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 epic to target the "4.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
@jhernand: 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-sigs/prow repository. I understand the commands that are listed here. |
Replaced by #7096. |
This patch adds support for using an external load balancer. It will only be available for OpenShift 4.16 or newer. To enable it the user will have to use the new
load_balancer.type
field of thecluster
type, for example:To preserve backwards compatibility this will be optional, and the
default value will be
cluster-managed
.When the value is
user-managed
the following will be added to thegenerated
install-config.yaml
file:The database will be automatically migrated so that for existing
clusters the value of the
load_balancer_type
column will automaticallybe set to
cluster-managed
.This patch adds this support only for the
baremetal
andvsphere
platforms.
Note that when using an external load balancer the VIPs will not be
used, but we are still requiring them, and using them to calculate the
machine CIDR. Insted we should validate that no VIPs are given, and we
should calculate the machine CIDR in some other way. That is not part of
this patch.
List all the issues related to this PR
https://issues.redhat.com/browse/MGMT-18913
What environments does this code impact?
How was this code tested?
Checklist
docs
, README, etc)Reviewers Checklist