Skip to content

Support for network changes starting with Istio v1.10 and greater #2538

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.

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 9 commits into from
Sep 21, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
32 changes: 32 additions & 0 deletions documentation/staging/content/userguide/istio/istio.md
Original file line number Diff line number Diff line change
Expand Up @@ -142,6 +142,38 @@ If the WebLogic administration port is enabled on the Administration Server:
Additionally, when Istio support is enabled for a domain, the operator
ensures that the Istio sidecar is not injected into the introspector job's pods.

#### Support for network changes in Istio v1.10 and later

Starting with Istio 1.10, the networking behavior was changed in that the proxy no longer redirects
the traffic to the localhost interface, but instead forwards it to the network interface associated
with the pod's IP.

To learn more about changes to Istio networking beginning with Istio 1.10, see [Upcoming networking changes in Istio 1.10](https://istio.io/latest/blog/2021/upcoming-networking-changes/).

In order to support Istio v1.10 and later, as well as previous releases, the
operator will:

* Add an additional WebLogic HTTP protocol network channel for the readiness probe that is bound to the localhost network interface.
* Add additional WebLogic network channels, bound to the localhost network interface, for each defined custom network channel.
* Continue to automatically add the network channels described above in [How Istio-enabled domains differ from regular domains](#how-istio-enabled-domains-differ-from-regular-domains)

When adding additional WebLogic network channels for the readiness probe and any defined custom channels,
the name of the additional channel will be appended with '-lhNN', where NN represents
a two digit value for uniqueness.

For example, the additional WebLogic HTTP protocol network channel for the readiness probe would be
defined as follows:

|Name|Port|Listening address|Protocol|Exposed as a container port|
|----|----|----|--------|-----|
|`http-probe-lh01`|From configuration Istio `readinessPort` | `127.0.0.1` | `http`| No |

As another example, for a custom WebLogic network channel defined as `T3Channel` with port `5556`
and protocol `t3`, the additional channel would be defined as follows:

|Name|Port|Listening address|Protocol|Exposed as a container port|
|----|----|----|--------|-----|
|`T3Channel-lh01`| `5556` | `127.0.0.1` | `t3`| Yes |

### Apply the Domain YAML file

Expand Down
Loading