Skip to content

Commit 238f3f3

Browse files
authored
followup docs changes (#327)
1 parent 079575e commit 238f3f3

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/modules/listener-operator/pages/listenerclass.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Think of it as a policy that says "when an application asks for 'external-stable
66

77
== Common Examples
88

9-
=== Cloud Environment (GKE, EKS, AKS)
9+
=== Cloud Environment (GKE, EKS, AKS and others)
1010

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

@@ -201,13 +201,13 @@ spec:
201201
[#addresstype]
202202
=== Address Types
203203

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

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

210-
This means that we default to hostnames where "safe", but don't assume that nodes are resolvable by external clients.
210+
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.
211211

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

0 commit comments

Comments
 (0)