Skip to content

OSDOCS-19483] Addresses comment made for OSDOCS 19483 #111695

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.

Sign up for GitHub

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

Open
stevsmit wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −0
Open

OSDOCS-19483] Addresses comment made for OSDOCS 19483 #111695

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions modules/nw-ingress-gateway-api-enable.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,6 +145,12 @@ $ oc get deployment -n openshift-ingress example-gateway-openshift-default
NAME READY UP-TO-DATE AVAILABLE AGE
example-gateway-openshift-default 1/1 1 1 25s
----
+
[NOTE]
====
The difference between highly available and non-highly-available topologies is the minimum number of replicas: at least two on highly available clusters, and one on clusters that do not use a highly available topology. Either topology can scale a gateway deployment out to ten replicas.
Copy link
Copy Markdown
Contributor

@snarayan-redhat snarayan-redhat May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Using at least might be redundant since you have already specified minimum number.
This is nitty nit. So all good to merge. :)

Copy link
Copy Markdown
Member Author

@stevsmit stevsmit May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Will definitely consider this after dev review! :)

Copy link
Copy Markdown

@melvinjoseph86 melvinjoseph86 May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Steve, if you mention either topology can scale to 10, then it will be not non ha (it will become redundant cluster). so better make similar to below.

The difference between high available and non-high-available topologies is the minimum number of replicas: at least two gateway instances on high available clusters(which can scale out to ten replicas), and only one gateway instance on the cluster that do not use a high available topology.

====

*** To verify the service, run the following command:
+
[source,terminal]
Expand Down