Skip to content

Commit 647842c

Browse files
authored
Merge pull request #78503 from dfitzmau/OSDOCS-9350-feedback
[internal-fix] OSDOCS-9350-feedback: Addressed feedback from OSDOCS-9350
2 parents 6d84f31 + 040436b commit 647842c

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

modules/nw-ingress-controller-configuration-parameters.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
[id="nw-ingress-controller-configuration-parameters_{context}"]
77
= Ingress Controller configuration parameters
88

9-
The `ingresscontrollers.operator.openshift.io` resource includes optional configuration parameters that you can configure to meet specific needs for your organization.
9+
The `Infrastructure` custom resource (CR) includes optional configuration parameters that you can configure to meet specific needs for your organization.
1010

1111
[cols="3a,8a",options="header"]
1212
|===
@@ -67,7 +67,7 @@ endif::openshift-rosa[]
6767
ifndef::openshift-rosa,openshift-dedicated[]
6868
For non-cloud environments, such as a bare-metal platform, use the `NodePortService`, `HostNetwork`, or `Private` fields to configure the endpoint publishing strategy for your Ingress Controller.
6969

70-
If you do not set a value in one of these fields, the default value is based on binding ports specified in the `infrastructure.config.openshift.io/cluster` `.status.platform` resource.
70+
If you do not set a value in one of these fields, the default value is based on binding ports specified in the `.status.platform` value in the `Infrastructure` CR.
7171
endif::openshift-rosa,openshift-dedicated[]
7272

7373
ifndef::openshift-rosa[]

networking/nw-configuring-ingress-controller-endpoint-publishing-strategy.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ The `endpointPublishingStrategy` is used to publish the Ingress Controller endpo
1010

1111
[IMPORTANT]
1212
====
13-
On {rh-openstack-first}, the `LoadBalancerService` endpoint publishing strategy is only supported if a cloud provider is configured to create health monitors. For {rh-openstack} 16.2, this strategy is only possible if you use the Amphora Octavia provider.
13+
On {rh-openstack-first}, the `LoadBalancerService` endpoint publishing strategy is supported only if a cloud provider is configured to create health monitors. For {rh-openstack} 16.2, this strategy is possible only if you use the Amphora Octavia provider.
1414
15-
For more information, see the " Setting {rh-openstack} Cloud Controller Manager options" section of the {rh-openstack} installation documentation.
15+
For more information, see the "Setting {rh-openstack} Cloud Controller Manager options" section of the {rh-openstack} installation documentation.
1616
====
1717

1818
// Ingress Controller endpoint publishing strategy

0 commit comments

Comments
 (0)