-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
OSDOCS-6962_RN#adding release note #86899
OSDOCS-6962_RN#adding release note #86899
Conversation
🤖 Tue Jan 21 09:59:27 - Prow CI generated the docs preview: |
b8f1a06
to
8cb6bdf
Compare
@@ -419,6 +419,12 @@ For more information, see xref:../nodes/clusters/nodes-cluster-enabling-features | |||
[id="ocp-release-notes-installation-and-update_{context}"] | |||
=== Installation and update | |||
|
|||
[id="ocp-4.18-installation-and-update-byoip-ovn_{context}"] | |||
==== Bring your own IPv4 (BYOIP) join subnet feature is enabled on `ovn-kubernetes` for Virtual Private Cloud (VPC) | |||
With this release, you can configure the IPv4 join subnet that is used internally by `ovn-kubernetes` in a Bring your own (BYO) Virtual Private Cloud (VPC). You can set the `OVNKubernetesConfig` parameter in the `install-config.yaml` file and deploy the cluster into an existing VPC. |
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.
With this release, you can configure the IPv4 join subnet that is used internally by `ovn-kubernetes` in a Bring your own (BYO) Virtual Private Cloud (VPC). You can set the `OVNKubernetesConfig` parameter in the `install-config.yaml` file and deploy the cluster into an existing VPC. | |
With this release, you can configure the IPv4 join subnet that is used internally by `ovn-kubernetes` when installing a cluster into an existing Virtual Private Cloud (VPC). You can set the `internalJoinSubnet` parameter in the `install-config.yaml` file and deploy the cluster into an existing VPC. |
8cb6bdf
to
c6a6b72
Compare
@yunjiang29, PTAL at the draft release note. |
@@ -419,6 +419,12 @@ For more information, see xref:../nodes/clusters/nodes-cluster-enabling-features | |||
[id="ocp-release-notes-installation-and-update_{context}"] | |||
=== Installation and update | |||
|
|||
[id="ocp-4.18-installation-and-update-byoip-ovn_{context}"] | |||
==== Bring your own IPv4 (BYOIP) join subnet feature is enabled on `ovn-kubernetes` for Virtual Private Cloud (VPC) |
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.
Searching the existing document, BYOIP
refers to Bring your own public IPv4 addresses [1], which is for publicIpv4Pool field, but internalJoinSubnet uses internal/private addresses, I think we can update the title like Add support to configure IPv4 subnet to customize internal OVN network to reduce the confusion.
@patrickdillon do you have any idea about the title?
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.
Maybe something like
Install-time configuration for the ovn-kubernetes
join subnet is now enabled
@@ -419,6 +419,12 @@ For more information, see xref:../nodes/clusters/nodes-cluster-enabling-features | |||
[id="ocp-release-notes-installation-and-update_{context}"] | |||
=== Installation and update | |||
|
|||
[id="ocp-4.18-installation-and-update-byoip-ovn_{context}"] | |||
==== Bring your own IPv4 (BYOIP) join subnet feature is enabled on `ovn-kubernetes` for Virtual Private Cloud (VPC) | |||
With this release, you can configure the IPv4 join subnet that is used internally by `ovn-kubernetes` when installing a cluster into an existing Virtual Private Cloud (VPC). You can set the `internalJoinSubnet` parameter in the `install-config.yaml` file and deploy the cluster into an existing VPC. |
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.
This feature is not limited to BYO-VPC:
With this release, you can configure the IPv4 join subnet that is used internally by `ovn-kubernetes` when installing a cluster into an existing Virtual Private Cloud (VPC). You can set the `internalJoinSubnet` parameter in the `install-config.yaml` file and deploy the cluster into an existing VPC. | |
With this release, you can configure the IPv4 join subnet that is used internally by `ovn-kubernetes` when installing a cluster. You can set the `internalJoinSubnet` parameter in the `install-config.yaml` file and deploy the cluster into an existing VPC. |
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.
+1 it is not limited to byo-vpc. That said, byo vpc is the primary use case. Suggested changes look good.
c6a6b72
to
783f804
Compare
64f85ed
to
c66fd11
Compare
/label peer-review-needed |
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.
One comment on the heading otherwise LGTM
@@ -419,6 +419,12 @@ For more information, see xref:../nodes/clusters/nodes-cluster-enabling-features | |||
[id="ocp-release-notes-installation-and-update_{context}"] | |||
=== Installation and update | |||
|
|||
[id="ocp-4.18-installation-and-update-ovn-kubernetes-join-subnet_{context}"] | |||
==== Install-time configuration for the `ovn-kubernetes` join subnet feature is enabled |
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.
==== Install-time configuration for the `ovn-kubernetes` join subnet feature is enabled | |
==== Configuring the ovn-kubernetes join subnet during cluster installation |
OR
==== Install-time configuration for the `ovn-kubernetes` join subnet feature is enabled | |
==== Configuring the IPV4 join subnet during cluster installation |
Instead of "Install-time" I think "during cluster installation" is clearer.
08a578d
to
a5d46d5
Compare
/label merge-review-needed |
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.
A nit, but might as well fix up before merge.
Please re-queue when ready. Thank you!
@@ -419,6 +419,12 @@ For more information, see xref:../nodes/clusters/nodes-cluster-enabling-features | |||
[id="ocp-release-notes-installation-and-update_{context}"] | |||
=== Installation and update | |||
|
|||
[id="ocp-4.18-installation-and-update-ovn-kubernetes-join-subnet_{context}"] |
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.
No .
s in IDs:
[id="ocp-4.18-installation-and-update-ovn-kubernetes-join-subnet_{context}"] | |
[id="ocp-4-18-installation-and-update-ovn-kubernetes-join-subnet_{context}"] |
a5d46d5
to
5b67ae5
Compare
5b67ae5
to
2908934
Compare
@brendan-daly-red-hat: 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-sigs/prow repository. I understand the commands that are listed here. |
/label merge-review-needed |
Version:
4.18
Issue:
https://issues.redhat.com/browse/OSDOCS-6962
Link to docs preview:
Configuring the ovn-kubernetes join subnet during cluster installation
QE review:
Additional information: