-
Notifications
You must be signed in to change notification settings - Fork 580
Bug 1894268: Allow users to specify ovnkube join subnet #1207
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
Conversation
|
Hello @pliurh! Some important instructions when contributing to openshift/api: For merging purposes, this repository follows the no-Feature-Freeze process which means that in addition to the standard
OR
Who should apply these qe/docs/px labels?
|
|
@pliurh: This pull request references Bugzilla bug 1894268, which is invalid:
Comment 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. |
|
It is to continue the work of #824 |
|
/cc @danwinship |
operator/v1/types_network.go
Outdated
| // v4InternalSubnet is the v4 join subnet to be used by ovn-kubernetes in case the | ||
| // default one is being already used by something else. | ||
| // Default is 100.64.0.0/16 |
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.
"join subnet" is meaningless to the user. "is a v4 subnet used internally by ovn-kubernetes".
"Must not overlap with any other subnet being used by OpenShift or by the node network"
Needs a hint about how big it needs to be. (Does it depend on the cluster size? Number of nodes? Number of pods?)
Can this be changed after install or does it need to be set at install time?
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.
fixed.
Some users need to be able to specify the v4 and v6 join subnets to use for ovn-k. In particular, they may be already using the ones that ovn-k uses as default, and they need a way to be able to specify a different set of subnets as join subnets. This commit creates the config option for the same. Eventually this will be consumed by the CNO using rendered bootstrap data and passed to the ovn-k daemonsets. Signed-off-by: Peng Liu <pliu@redhat.com>
|
/bugzilla refresh |
|
@pliurh: This pull request references Bugzilla bug 1894268, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
I suppose if we are going to make this user-configurable, then this PR is fine. |
|
@jboxman @huiran0826 PTAL. |
|
lgtm, @weliang1 Could you help take a look as well? |
|
This is the story link https://issues.redhat.com/browse/SDN-2593. |
|
/label docs-approved |
/lgtm |
|
/label qe-approved |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, knobunc, pliurh, weliang1 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 |
|
@pliurh: all tests passed! 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. |
|
@pliurh: All pull requests linked via external trackers have merged: Bugzilla bug 1894268 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. |
Some users need to be able to specify the v4 and v6 join subnets
to use for ovn-k. In particular, they may be already using the
ones that ovn-k uses as default, and they need a way to be able to
specify a different set of subnets as join subnets. This commit
creates the config option for the same. Eventually this will be
consumed by the CNO using rendered bootstrap data and passed to the
ovn-k daemonsets.
Signed-off-by: Peng Liu pliu@redhat.com