Skip to content

Commit d9c5347

Browse files
authored
Clarify what are valid names for listeners on GKE (#752)
1 parent c1a31b5 commit d9c5347

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

website/docs.md

+5
Original file line numberDiff line numberDiff line change
@@ -2457,6 +2457,11 @@ internet. By default, all listeners are **private**, i.e., accessible only from
24572457
the cloud project's internal network. In our example, we declare that the
24582458
`hello` listener is public.
24592459

2460+
**Note**: Per RFC1035 and RFC1123, listener names should respect the following
2461+
pattern: `^(\*\.)?[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`.
2462+
Listener names must consist of lower case alphanumeric characters or '-', and
2463+
must start and end with an alphanumeric character. No other punctuation is allowed.
2464+
24602465
All listeners deployed to GKE are configured to be health-checked by GKE
24612466
load-balancers on the `/debug/weaver/healthz` URL path. ServiceWeaver
24622467
automatically registers a health-check handler under this URL path in the

0 commit comments

Comments
 (0)