OSDOCS-16862: CQA2.0 of CORE-3: Ingress Controllers and Load Balancin… #104156

dfitzmau · 2025-12-18T15:50:25Z

Version(s):
4.16+

Link to docs preview:

Continue next PR from networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc

openshift-ci-robot · 2025-12-18T15:50:30Z

@dfitzmau: This pull request references OSDOCS-16862 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.16+

Issue:
OSDOCS-16862

Link to docs preview:

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.

ocpdocs-previewbot · 2025-12-18T16:00:25Z

🤖 Fri Dec 19 17:01:29 - Prow CI generated the docs preview:
https://104156--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

openshift-ci-robot · 2025-12-18T16:25:11Z

@dfitzmau: This pull request references OSDOCS-16862 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.16+

Issue:
OSDOCS-16862

Link to docs preview:

penshift-docs/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-patch-fields.adoc'

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.

openshift-ci-robot · 2025-12-18T16:26:09Z

@dfitzmau: This pull request references OSDOCS-16862 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.16+

Issue:
OSDOCS-16862

Link to docs preview:

Allocating Load Balancers to Specific Subnets

Configuring ExternalIPs for services

penshift-docs/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-patch-fields.adoc'

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.

openshift-ci-robot · 2025-12-19T14:51:05Z

@dfitzmau: This pull request references OSDOCS-16862 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.16+

Issue:
OSDOCS-16862

Link to docs preview:

Allocating Load Balancers to Specific Subnets

Configuring ExternalIPs for services

penshift-docs/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-patch-fields.adoc'

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.

…g Overview

openshift-ci-robot · 2025-12-19T16:53:24Z

@dfitzmau: This pull request references OSDOCS-16862 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.16+

Issue:
OSDOCS-16862

Link to docs preview:

etworking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc'

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.

openshift-ci · 2025-12-19T17:05:48Z

@dfitzmau: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

openshift-ci-robot · 2025-12-22T11:06:09Z

@dfitzmau: This pull request references OSDOCS-16862 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.16+

Issue:
OSDOCS-16862

Link to docs preview:

Continue next PR from networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc

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.

openshift-ci-robot · 2025-12-22T11:06:47Z

@dfitzmau: This pull request references OSDOCS-16862 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Version(s):
4.16+

Issue:
OSDOCS-16862

Link to docs preview:

https://104156--ocpdocs-pr.netlify.app/openshift-dedicated/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html

https://104156--ocpdocs-pr.netlify.app/openshift-dedicated/latest/networking/ingress_load_balancing/routes/nw-configuring-routes.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_aws/ipi/installing-aws-customizations.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/allocating-load-balancers.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-externalip.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-patch-fields.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/routes/nw-configuring-routes.html

https://104156--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html

https://104156--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/networking/ingress_load_balancing/routes/nw-configuring-routes.html

https://104156--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html

https://104156--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/ingress_load_balancing/routes/nw-configuring-routes.html

Continue next PR from networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc

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.

mburke5678 · 2025-12-22T18:12:56Z

modules/nw-allocate-load-balancers-to-subnets-procedure.adoc

+.Prerequisites

+* An existing AWS virtual private cloud (VPC).
+* Pre-configured AWS subnets intended for use by the OpenShift cluster, with the following considerations:


Suggested change

* Pre-configured AWS subnets intended for use by the OpenShift cluster, with the following considerations:

* Pre-configured AWS subnets intended for use by the {product-title} cluster, with the following considerations:

mburke5678 · 2025-12-22T19:05:22Z

modules/nw-allocate-load-balancers-to-subnets-procedure.adoc

+`baseDomain`:: Your base domain.
+`region`:: Your AWS region.
+`vpc`:: The vpc object under `platform.aws` contains the subnets list.
+`subnets`:: List of all subnet objects that OpenShift will use. Each object defines a subnet id and its roles.
+`id`:: Replace with your AWS Subnet ID. 
+`type.IngressControllerLB`:: The `type: IngressControllerLB` role specifically designates this subnet for the default Ingress Controller's LoadBalancer. In private/internal cluster, the subnet with `IngressControllerLB` role must be private.
+`type.ClusterNode`:: The `type: ClusterNode` role designates this subnet for control plane and compute nodes. These are typically private subnets.
+`pullSecret`:: Your pull secret.
+`sshKey`:: Your SSH key.


Doc guidelines: introduce the description list with "where:" and start each variable description with "Specifies."

Suggested change

`baseDomain`:: Your base domain.

`region`:: Your AWS region.

`vpc`:: The vpc object under `platform.aws` contains the subnets list.

`subnets`:: List of all subnet objects that OpenShift will use. Each object defines a subnet id and its roles.

`id`:: Replace with your AWS Subnet ID.

`type.IngressControllerLB`:: The `type: IngressControllerLB` role specifically designates this subnet for the default Ingress Controller's LoadBalancer. In private/internal cluster, the subnet with `IngressControllerLB` role must be private.

`type.ClusterNode`:: The `type: ClusterNode` role designates this subnet for control plane and compute nodes. These are typically private subnets.

`pullSecret`:: Your pull secret.

`sshKey`:: Your SSH key.

`baseDomain`:: Specifies your base domain.

`region`:: Specifies your AWS region.

`vpc`:: Specifies the vpc object under `platform.aws` contains the subnets list.

`subnets`:: Specifies a list of all subnet objects that OpenShift will use. Each object defines a subnet id and its roles.

`id`:: Specifies your AWS Subnet ID.

`type.IngressControllerLB`:: Specifies this subnet for the default Ingress Controller's LoadBalancer. In private/internal cluster, the subnet with `IngressControllerLB` role must be private.

`type.ClusterNode`:: Specifies the `type: ClusterNode` role designates this subnet for control plane and compute nodes. These are typically private subnets.

`pullSecret`:: Specifies your pull secret.

`sshKey`:: Specifies your SSH key.

mburke5678 · 2025-12-22T19:08:33Z

modules/nw-aws-nlb-existing-cluster.adoc

+where:
+
+`<ingress_controller_name>`: Replace `<ingress_controller_name>` with a unique name for the Ingress Controller.
+`<unique_ingress_domain>`:: Replace `<unique_ingress_domain>` with a domain name that is unique among all Ingress Controllers in the cluster. This variable must be a subdomain of the DNS name `<clustername>.<domain>`.
+`scope`:: You can replace `External` with `Internal` to use an internal NLB.


Suggested change

where:

+

`<ingress_controller_name>`: Replace `<ingress_controller_name>` with a unique name for the Ingress Controller.

`<unique_ingress_domain>`:: Replace `<unique_ingress_domain>` with a domain name that is unique among all Ingress Controllers in the cluster. This variable must be a subdomain of the DNS name `<clustername>.<domain>`.

`scope`:: You can replace `External` with `Internal` to use an internal NLB.

where:

+

`<ingress_controller_name>`: Specifies a unique name for the Ingress Controller.

`<unique_ingress_domain>`:: Specifies a domain name that is unique among all Ingress Controllers in the cluster. This variable must be a subdomain of the DNS name `<clustername>.<domain>`.

`scope`:: Specifies the type of NLB, either `External` to use an external NLB or `Internal` to use an internal NLB.

mburke5678 · 2025-12-22T19:09:45Z

modules/nw-aws-nlb-new-cluster.adoc

+$ touch <installation_directory>/manifests/cluster-ingress-default-ingresscontroller.yaml
 ----
-<1> For `<installation_directory>`, specify the directory name that contains the
+`<installation_directory>`:: For `<installation_directory>`, specify the directory name that contains the


Suggested change

`<installation_directory>`:: For `<installation_directory>`, specify the directory name that contains the

`<installation_directory>`:: Specifies the directory name that contains the

mburke5678 · 2025-12-22T19:13:47Z

modules/configuration-externalip.adoc

+[role="_abstract"]
+You can set parameters in the `Network.config.openshift.io` custom resource (CR) to govern the use of an external IP address in {product-title}. These parameters are listed as follows:


I'm not sure that this second, introductory, sentence belongs in the abstract. I fear it will get caught up in the DITA short description and get separated from the bullet list that the sentence introduces. (But that is a guess on my part. I started a Slack chat asking about it, but nothing so far.)

mburke5678 · 2025-12-22T19:25:33Z

modules/nw-ingress-aws-static-eip-nlb-configuration.adoc

+where:
+
+`<name>`:: Replace the `<name>` placeholder with a name for the Ingress Controller.
+`<domain>`:: Replace the `<domain>` placeholder with the DNS name serviced by the Ingress Controller.
+`scope`:: The scope must be set to the value `External` and be Internet-facing in order to allocate EIPs.
+`subnets:: Specify the IDs and names for your subnets. The total number of IDs and names must be equal to your allocated EIPs.
+`eipAllocations`:: Specify the EIP addresses.


Suggested change

where:

+

`<name>`:: Replace the `<name>` placeholder with a name for the Ingress Controller.

`<domain>`:: Replace the `<domain>` placeholder with the DNS name serviced by the Ingress Controller.

`scope`:: The scope must be set to the value `External` and be Internet-facing in order to allocate EIPs.

`subnets:: Specify the IDs and names for your subnets. The total number of IDs and names must be equal to your allocated EIPs.

`eipAllocations`:: Specify the EIP addresses.

where:

+

`<name>`:: Specifies a name for the Ingress Controller.

`<domain>`:: Specifies the DNS name serviced by the Ingress Controller.

`scope`:: Specifies a scope for the EIPs. The scope must be set to the value `External` and be Internet-facing in order to allocate EIPs.

`subnets:: Specifies the IDs and names for your subnets. The total number of IDs and names must be equal to your allocated EIPs.

`eipAllocations`:: Specifies the EIP addresses.

mburke5678 · 2025-12-22T19:33:31Z

modules/nw-ingress-setting-select-subnet-loadbalancerservice.adoc

+where:
+
+`name`:: Replace `<name>` with a name for the `IngressController`.
+`domain`:: Replace `<domain>` with the DNS name serviced by the `IngressController`.
+`classicLoadBalancer`:: You can also use the `networkLoadBalancer` field if using an NLB.
+`ids`:: You can optionally specify a subnet by name using the `names` field instead of specifying the subnet by ID.
+`<subnet>`:: Specify subnet IDs (or names if you using `names`).


Suggested change

where:

+

`name`:: Replace `<name>` with a name for the `IngressController`.

`domain`:: Replace `<domain>` with the DNS name serviced by the `IngressController`.

`classicLoadBalancer`:: You can also use the `networkLoadBalancer` field if using an NLB.

`ids`:: You can optionally specify a subnet by name using the `names` field instead of specifying the subnet by ID.

`<subnet>`:: Specify subnet IDs (or names if you using `names`).

where:

+

`name`:: Specifies a name for the `IngressController`.

`domain`:: Specifies the DNS name serviced by the `IngressController`.

`classicLoadBalancer`:: Specifies the type of load balancer, either `classicLoadBalancer` if using a CLB or `networkLoadBalancer` field if using an NLB.

`ids`:: Specifies a subnet by name using the `names` field instead of specifying the subnet by ID. This field is optional.

`<subnet>`:: Specifies the subnet IDs (or names if you using `names`).

mburke5678 · 2025-12-22T19:34:47Z

modules/nw-ingress-setting-update-subnet-loadbalancerservice.adoc

+[role="_abstract"]
+You can update an `IngressController` with manually specified load balancer subnets in {product-title} to avoid any disruptions, to maintain the stability of your services, and to ensure that your network configuration aligns with your specific requirements. The example in the procedure shows you how to select and apply new subnets, verify the configuration changes, and confirm successful load balancer provisioning. 


Again, do we need to split out the The example in the procedure from the abstract??

mburke5678 · 2025-12-22T19:36:49Z

modules/nw-ingress-setting-update-subnet-loadbalancerservice.adoc

+where:
+
+`<name>`:: Replace `<name>` with a name for the `IngressController`.
+`<domain>`:: Replace `<domain>` with the DNS name serviced by the `IngressController`.
+`type`:: Specify updated subnet IDs (or names if you using `names`).
+`classicLoadBalancer`:: You can also use the `networkLoadBalancer` field if using an NLB.
+`ids`:: You can optionally specify a subnet by name using the `names` field instead of specifying the subnet by ID.
+`<updated_subnet>`:: Update subnet IDs (or names if you are using `names`).


Suggested change

where:

+

`<name>`:: Replace `<name>` with a name for the `IngressController`.

`<domain>`:: Replace `<domain>` with the DNS name serviced by the `IngressController`.

`type`:: Specify updated subnet IDs (or names if you using `names`).

`classicLoadBalancer`:: You can also use the `networkLoadBalancer` field if using an NLB.

`ids`:: You can optionally specify a subnet by name using the `names` field instead of specifying the subnet by ID.

`<updated_subnet>`:: Update subnet IDs (or names if you are using `names`).

where:

+

`<name>`:: Specifies a name for the `IngressController`.

`<domain>`:: Specifies the DNS name serviced by the `IngressController`.

`type`:: Specifies the updated subnet IDs (or names if you using `names`).

`classicLoadBalancer`:: You can also use the `networkLoadBalancer` field if using an NLB.

`ids`:: Specifies the subnet by name using the `names` field instead of specifying the subnet by ID. This parameter is optional.

`<updated_subnet>`:: Specifies the updated subnet IDs (or names if you are using `names`).

mburke5678 · 2025-12-22T19:39:07Z

modules/nw-ingress-sharding-route-configuration.adoc

+where:
+
+`type`:: Both the label key and its corresponding label value must match the ones specified in the Ingress Controller. In this example, the Ingress Controller has the label key and value `type: sharded`.
+`subdomain`:: The route gets exposed by using the value of the `subdomain` field. When you specify the `subdomain` field, you must leave the hostname unset. If you specify both the `host` and `subdomain` fields, then the route uses the value of the `host` field, and ignore the `subdomain` field.


Suggested change

where:

+

`type`:: Both the label key and its corresponding label value must match the ones specified in the Ingress Controller. In this example, the Ingress Controller has the label key and value `type: sharded`.

`subdomain`:: The route gets exposed by using the value of the `subdomain` field. When you specify the `subdomain` field, you must leave the hostname unset. If you specify both the `host` and `subdomain` fields, then the route uses the value of the `host` field, and ignore the `subdomain` field.

where:

+

`type`:: Specifies both the label key and its corresponding label value must match the ones specified in the Ingress Controller. In this example, the Ingress Controller has the label key and value `type: sharded`.

`subdomain`:: Specifies the route gets exposed by using the value of the `subdomain` field. When you specify the `subdomain` field, you must leave the hostname unset. If you specify both the `host` and `subdomain` fields, then the route uses the value of the `host` field, and ignore the `subdomain` field.

mburke5678 · 2025-12-22T19:50:26Z

modules/nw-ingress-sharding-route-configuration.adoc

+where:
+
+`host`:: The hostname the Ingress Controller, or router, uses to expose the route. The value of the `host` field is automatically determined by the Ingress Controller, and uses its domain. In this example, the domain of the Ingress Controller is `<apps-sharded.basedomain.example.net>`. 
+`<apps-sharded.basedomain.example.net>`:: The hostname of the Ingress Controller. If the hostname is not set, the route can use a subdomain instead. When you specify a subdomain, you automatically use the domain of the Ingress Controller that exposes the route. When a route is exposed by multiple Ingress Controllers, the route is hosted at multiple URLs.
+`routerName`:: The name of the Ingress Controller. In this example, the Ingress Controller has the name `sharded`.


Suggested change

where:

+

`host`:: The hostname the Ingress Controller, or router, uses to expose the route. The value of the `host` field is automatically determined by the Ingress Controller, and uses its domain. In this example, the domain of the Ingress Controller is `<apps-sharded.basedomain.example.net>`.

`<apps-sharded.basedomain.example.net>`:: The hostname of the Ingress Controller. If the hostname is not set, the route can use a subdomain instead. When you specify a subdomain, you automatically use the domain of the Ingress Controller that exposes the route. When a route is exposed by multiple Ingress Controllers, the route is hosted at multiple URLs.

`routerName`:: The name of the Ingress Controller. In this example, the Ingress Controller has the name `sharded`.

where:

+

`host`:: Specifies the hostname that the Ingress Controller, or router, uses to expose the route. The value of the `host` field is automatically determined by the Ingress Controller, and uses its domain. In this example, the domain of the Ingress Controller is `<apps-sharded.basedomain.example.net>`.

`<apps-sharded.basedomain.example.net>`:: Specifies the hostname of the Ingress Controller. If the hostname is not set, the route can use a subdomain instead. When you specify a subdomain, you automatically use the domain of the Ingress Controller that exposes the route. When a route is exposed by multiple Ingress Controllers, the route is hosted at multiple URLs.

`routerName`:: Specifies the name of the Ingress Controller. In this example, the Ingress Controller has the name `sharded`.

mburke5678 · 2025-12-22T19:52:00Z

modules/nw-patch-fields-example.adoc

+====

-.Procedure
+THe procedure demonstrates patching the `Ingress` objects with a completed `ingressClassName` field to ensure proper routing and functionality.


Suggested change

THe procedure demonstrates patching the `Ingress` objects with a completed `ingressClassName` field to ensure proper routing and functionality.

The procedure demonstrates patching the `Ingress` objects with a completed `ingressClassName` field to ensure proper routing and functionality.

mburke5678 · 2025-12-22T19:55:33Z

...rking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-externalip.adoc


-As a cluster administrator, you can select an IP address block that is external to the cluster that can send traffic to services in the cluster.
+[role="_abstract"]
+As a cluster administrator, you can select an IP address block that is external to the cluster that can send traffic to services in the cluster. This functionality is generally most useful for clusters installed on bare-metal hardware.


Nit for clarity:

Suggested change

As a cluster administrator, you can select an IP address block that is external to the cluster that can send traffic to services in the cluster. This functionality is generally most useful for clusters installed on bare-metal hardware.

As a cluster administrator, you can select an IP address block that is external to the cluster and can send traffic to services in the cluster. This functionality is generally most useful for clusters installed on bare-metal hardware.

mburke5678 · 2025-12-22T19:58:53Z

...d_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc

-====
-Before you can configure an Ingress Controller NLB on a new AWS cluster, you must complete the xref:../../../installing/installing_aws/ipi/installing-aws-customizations.adoc#installation-initializing_installing-aws-customizations[Creating the installation configuration file] procedure.
-====
+[role="_additional-resources"]


Do we want to save this note? Seems important......

Before you can configure an Ingress Controller NLB on a new AWS cluster, you must complete the installation configuration file procedure. For more information, see "Creating the installation configuration file."

mburke5678 · 2025-12-22T21:18:01Z

modules/nw-allocate-load-balancers-to-subnets-procedure.adoc


-.Prerequisites
+When defining entries for control plane load balancers in the `subnets` list, ensure that you adhere to the following pattern:
+


Don't need the + here.

Suggested change

+

mburke5678 · 2025-12-22T21:23:42Z

Mostly DITA conversion concerns, peer-review-level suggestions, a couple of typos:

https://github.com/openshift/openshift-docs/pull/104156/files#r2641060456
https://github.com/openshift/openshift-docs/pull/104156/files#r2641272044

Not sure what this PR covers exactly, but there are a still some callouts in modules in some of the assemblies in the previews:

https://104156--ocpdocs-pr.netlify.app/openshift-dedicated/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html#nw-path-based-routes_creating-basic-routes
https://104156--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html#nw-path-based-routes_creating-basic-routes
https://104156--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html#nw-path-based-routes_creating-basic-routes

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html#nw-ingress-creating-a-route-via-an-ingress_creating-basic-routes
https://104156--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/networking/ingress_load_balancing/routes/creating-basic-routes.html

https://104156--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ingress_load_balancing/routes/nw-configuring-routes.html#nw-route-set-or-delete-http-headers_configuring-routes

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 18, 2025

openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 18, 2025

dfitzmau force-pushed the OSDOCS-16862 branch 2 times, most recently from 794762c to e29a45e Compare December 18, 2025 16:24

dfitzmau added branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 branch/enterprise-4.20 labels Dec 18, 2025

dfitzmau force-pushed the OSDOCS-16862 branch 11 times, most recently from ba9834e to 9f5031e Compare December 19, 2025 14:48

dfitzmau force-pushed the OSDOCS-16862 branch 3 times, most recently from 8ec4021 to afdf9ff Compare December 19, 2025 16:30

openshift-ci bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 19, 2025

dfitzmau force-pushed the OSDOCS-16862 branch 2 times, most recently from c3e68f0 to 81213dd Compare December 19, 2025 16:50

OSDOCS-16862: CQA2.0 of CORE-3: Ingress Controllers and Load Balancin…

8f5c3a9

…g Overview

dfitzmau force-pushed the OSDOCS-16862 branch from 81213dd to 8f5c3a9 Compare December 19, 2025 16:52

dfitzmau added the merge-review-needed Signifies that the merge review team needs to review this PR label Dec 22, 2025

mburke5678 added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Dec 22, 2025

mburke5678 reviewed Dec 22, 2025

View reviewed changes

mburke5678 removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Dec 22, 2025

	* Pre-configured AWS subnets intended for use by the OpenShift cluster, with the following considerations:
	* Pre-configured AWS subnets intended for use by the {product-title} cluster, with the following considerations:

	`<installation_directory>`:: For `<installation_directory>`, specify the directory name that contains the
	`<installation_directory>`:: Specifies the directory name that contains the

		[role="_abstract"]
		You can set parameters in the `Network.config.openshift.io` custom resource (CR) to govern the use of an external IP address in {product-title}. These parameters are listed as follows:

		[role="_abstract"]
		You can update an `IngressController` with manually specified load balancer subnets in {product-title} to avoid any disruptions, to maintain the stability of your services, and to ensure that your network configuration aligns with your specific requirements. The example in the procedure shows you how to select and apply new subnets, verify the configuration changes, and confirm successful load balancer provisioning.

	THe procedure demonstrates patching the `Ingress` objects with a completed `ingressClassName` field to ensure proper routing and functionality.
	The procedure demonstrates patching the `Ingress` objects with a completed `ingressClassName` field to ensure proper routing and functionality.

	As a cluster administrator, you can select an IP address block that is external to the cluster that can send traffic to services in the cluster. This functionality is generally most useful for clusters installed on bare-metal hardware.
	As a cluster administrator, you can select an IP address block that is external to the cluster and can send traffic to services in the cluster. This functionality is generally most useful for clusters installed on bare-metal hardware.

OSDOCS-16862: CQA2.0 of CORE-3: Ingress Controllers and Load Balancin… #104156

Are you sure you want to change the base?

OSDOCS-16862: CQA2.0 of CORE-3: Ingress Controllers and Load Balancin… #104156

Uh oh!

Conversation

dfitzmau commented Dec 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 18, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ocpdocs-previewbot commented Dec 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 18, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 18, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 19, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 19, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Dec 19, 2025

Uh oh!

openshift-ci-robot commented Dec 22, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 22, 2025 • edited by openshift-ci bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mburke5678 commented Dec 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

dfitzmau commented Dec 18, 2025 •

edited

Loading

openshift-ci-robot commented Dec 18, 2025 •

edited by openshift-ci bot

Loading

ocpdocs-previewbot commented Dec 18, 2025 •

edited

Loading

openshift-ci-robot commented Dec 18, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Dec 18, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Dec 19, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Dec 19, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Dec 22, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Dec 22, 2025 •

edited by openshift-ci bot

Loading

mburke5678 commented Dec 22, 2025 •

edited

Loading