[WIP] OSDOCS-16402: CQA fixes for ROSA HCP Tutorials (part 1)#113885
[WIP] OSDOCS-16402: CQA fixes for ROSA HCP Tutorials (part 1)#113885otikhomi wants to merge 1 commit into
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@otikhomi: This pull request references OSDOCS-16402 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 "5.0.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
Bot
added
the
size/L
|
🤖 Mon Jun 22 22:58:08 - Prow CI generated the docs preview: |
| [TIP] | ||
| ==== | ||
| Load Balancers created by the AWS Load Balancer Operator cannot be used for xref:../networking/ingress_load_balancing/routes/nw-configuring-routes.adoc#route-configuration[OpenShift Routes], and should only be used for individual services or ingress resources that do not need the full layer 7 capabilities of an OpenShift Route. | ||
| Load Balancers created by the AWS Load Balancer Operator cannot be used for xref:../networking/ingress_load_balancing/routes/nw-configuring-routes.adoc#nw-configuring-routes[{OCP-short} Routes], and should only be used for individual services or ingress resources that do not need the full layer 7 capabilities of an {OCP-short} Route. |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
| ifndef::openshift-rosa-hcp[] | ||
| // Assembly configuring-egress-ips-ovn is commented out of the ROSA HCP topic map (as of June 2026). | ||
| ifdef::openshift-rosa[] | ||
| See xref:../networking/ovn_kubernetes_network_provider/configuring-egress-ips-ovn.adoc#configuring-egress-ips-ovn[Configuring an egress IP address] for more information. |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
| * The xref:../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[OpenShift CLI] (`oc`) | ||
| * The xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[ROSA CLI] (`rosa`) | ||
| * link:https://stedolan.github.io/jq/[`jq`] | ||
| * The xref:../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[{oc-first}] |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
| * The xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[ROSA CLI] (`rosa`) | ||
| * link:https://stedolan.github.io/jq/[`jq`] | ||
| * The xref:../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[{oc-first}] | ||
| * The xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[{rosa-cli-first}] |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
| * link:https://stedolan.github.io/jq/[`jq`] | ||
| * The xref:../cli_reference/openshift_cli/getting-started-cli.adoc#cli-getting-started[{oc-first}] | ||
| * The xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[{rosa-cli-first}] | ||
| * link:https://jqlang.org/[`jq`] |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
|
|
||
| [role="_abstract"] | ||
| A link:https://docs.aws.amazon.com/vpc/latest/userguide/DHCPOptionSet.html[custom DHCP option set] enables you to customize your VPC with your own DNS server, domain name, and more. {product-title} clusters support using custom DHCP option sets. By default, {product-title} clusters require setting the "domain name servers" option to `AmazonProvidedDNS` to ensure successful cluster creation and operation. Customers who want to use custom DNS servers for DNS resolution must do additional configuration to ensure successful {product-title} cluster creation and operation. | ||
| A link:https://docs.aws.amazon.com/vpc/latest/userguide/DHCPOptionSet.html[custom Dynamic Host Configuration Protocol (DHCP) option set] enables you to customize your Virtual Private Cloud (VPC) with your own Domain Name System (DNS) server, domain name, and more. {product-title} clusters support using custom DHCP option sets. By default, {product-title} clusters require setting the "domain name servers" option to `AmazonProvidedDNS` to ensure successful cluster creation and operation. Customers who want to use custom DNS servers for DNS resolution must do additional configuration to ensure successful {product-title} cluster creation and operation. |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
| A link:https://docs.aws.amazon.com/vpc/latest/userguide/DHCPOptionSet.html[custom Dynamic Host Configuration Protocol (DHCP) option set] enables you to customize your Virtual Private Cloud (VPC) with your own Domain Name System (DNS) server, domain name, and more. {product-title} clusters support using custom DHCP option sets. By default, {product-title} clusters require setting the "domain name servers" option to `AmazonProvidedDNS` to ensure successful cluster creation and operation. Customers who want to use custom DNS servers for DNS resolution must do additional configuration to ensure successful {product-title} cluster creation and operation. | ||
|
|
||
| In this tutorial, we will configure our DNS server to forward DNS lookups for specific DNS zones (further detailed below) to an link:https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html[Amazon Route 53 Inbound Resolver]. | ||
| In this tutorial, we will configure our DNS server to forward DNS lookups for specific DNS zones (further detailed below) to an link:https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html[Amazon Route 53 Inbound Resolver]. |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
| :_mod-docs-content-type: PROCEDURE | ||
| [id="cloud-experts-consistent-egress-ip-blocked-egress_{context}"] | ||
| = Optional: Testing blocked egress | ||
| = Optional: Test blocked egress |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoOptionalTitles: Do not begin a module or assembly title with 'Optional:'.
|
@otikhomi: 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-sigs/prow repository. I understand the commands that are listed here. |
| Complete the prerequisites before starting the web console deployment process. | ||
|
|
||
| The `rosa` CLI is required for certain tasks, such as creating the account roles. If you are deploying {product-title} for the first time, follow this the CLI steps until running the `rosa whoami` command, before starting the web console deployment steps. | ||
| The `rosa` CLI is required for certain tasks, such as creating the account roles. If you are deploying {product-title} for the first time, follow the CLI steps until running the `rosa whoami` command, before starting the web console deployment steps. |
There was a problem hiding this comment.
Do we keep rosa CLI in docs? Or should it always be ROSA CLI and hence {rosa-cli}.
otikhomi
changed the title
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
4 participants
Version(s):
4.22+
5.0+
Issue:
Main ROSA HCP Tutorials CQA ticket: https://redhat.atlassian.net/browse/OSDOCS-16402
Bug tickets:
Link to docs preview:
QE review:
N/A
Additional information:
CQA fixes for ROSA HCP Tutorials will be split into 2 PRs.
This PR 1 fixes: