Skip to content

Commit 77290a5

Browse files
committed
Clarify Service Entry addresses behavior limitations
Signed-off-by: Faseela K <faseela.k@est.tech>
1 parent dc36c0a commit 77290a5

File tree

3 files changed

+9
-3
lines changed

3 files changed

+9
-3
lines changed

networking/v1alpha3/service_entry.pb.go

Lines changed: 3 additions & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

networking/v1alpha3/service_entry.pb.html

Lines changed: 3 additions & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

networking/v1alpha3/service_entry.proto

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -482,7 +482,9 @@ message ServiceEntry {
482482
// service in the mesh. In other words, the sidecar will behave as a
483483
// simple TCP proxy, forwarding incoming traffic on a specified port to
484484
// the specified destination endpoint IP/host. Unix domain socket
485-
// addresses are not supported in this field.
485+
// addresses are not supported in this field. Note that the `addresses`
486+
// API implies you can provide multiple addresses but there are limitations
487+
// on it (e.g.: you cannot set VIP addresses regardless of the combination of ip families).
486488
// +kubebuilder:validation:MaxItems=256
487489
// +protoc-gen-crd:list-value-validation:MaxLength=64
488490
repeated string addresses = 2;

0 commit comments

Comments
 (0)