Skip to content

followup docs changes #327

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

Merged
merged 1 commit into from
Aug 12, 2025
Merged

followup docs changes #327

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: 3 additions & 3 deletions docs/modules/listener-operator/pages/listenerclass.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Think of it as a policy that says "when an application asks for 'external-stable

== Common Examples

=== Cloud Environment (GKE, EKS, AKS)
=== Cloud Environment (GKE, EKS, AKS and others)

In managed cloud environments, you typically want to use LoadBalancers since nodes are short-lived:

Expand Down Expand Up @@ -201,13 +201,13 @@ spec:
[#addresstype]
=== Address Types

Control whether clients receive IP addresses or hostnames:
Control whether IP addresses or hostnames are provided in the Listener status and filesystem:

`IP`:: Returns IP addresses (more compatible, less predictable especially for ClusterIP services)
`Hostname`:: Returns DNS hostnames (requires proper DNS setup)
`HostnameConservative`:: _(default)_ Uses hostnames for LoadBalancer/ClusterIP, IPs for NodePort

This means that we default to hostnames where "safe", but don't assume that nodes are resolvable by external clients.
LoadBalancer and ClusterIP services typically have reliable DNS names, but node hostnames may not be resolvable by external clients, so NodePort services get IP addresses instead.

NOTE: If the preferred address type is not supported for a given environment then another type will be used.

Expand Down
Loading