-
Notifications
You must be signed in to change notification settings - Fork 531
baremetal: Add bootstrap-external-ip #1071
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
baremetal: Add bootstrap-external-ip #1071
Conversation
|
|
||
| We will add a new field to the `install-config.yaml` file called | ||
| `bootstrapExternalIP`. This is similar to the existing | ||
| `bootstrapProvisioningIP` field. |
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.
Do we need to add additional validations for this new field? If so, what would they be?
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.
I think just verifying it's in the correct IP format should be fine.
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.
We should validate similar to other fields e.g
- IP syntax is valid
- IP is in the MachineNetwork
- IP doesn't conflict with other IPs (e.g API/Ingress VIP IPs)
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.
Thanks! I was wondering if there is some correlation with the networkConfig field. Since nothing is mentioned in the doc about it, I am assuming that they can occur independently. We could configure bootstrapExternalStaticIP, and
bootstrapExternalGateway irrespective of whether the networkConfig field is used to configure StaticIPs on hosts within the cluster.
zhouhao3
left a comment
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.
Seems good to me.
Is there a track issue for this proposal? I can help with some tasks for the implementation of this proposal if needed.
|
/lgtm |
| ## Design Details | ||
|
|
||
| ### Test Plan | ||
|
|
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.
We should follow up and add CI coverage for static IP deployments, I know @derekhiggins was working on that but I'm not sure of the latest status
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.
I stopped rebasing my PR when I saw had pushed a new version of his PR, @imain are you still working on it or will I rebase mine ? openshift-metal3/dev-scripts#1297
|
I agree with Steve's suggestion of stating which section of the install-config this will go in. Otherwise LGTM. |
2963a7c to
9ab8256
Compare
|
This version lgtm other than the markdownlint failure. We should follow up with the test-plan details though when we make progress on getting an e2e job in place that exercises the static-ip scenario (if you have to update this again perhaps mention there is work in-progress to add such coverage, and that this will get tested via that new job when it's done) |
29b1a54 to
56f0903
Compare
zaneb
left a comment
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.
/lgtm
56f0903 to
934c65e
Compare
|
/lgtm |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dtantsur The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@honza: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
No description provided.