- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 640 for traffic (0.18 sec)
-
releasenotes/notes/44777.yaml
apiVersion: release-notes/v2 kind: bug-fix area: traffic-management issue: - 41271 releaseNotes: - |
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon May 08 05:53:01 UTC 2023 - 196 bytes - Viewed (0) -
releasenotes/notes/48253.yaml
apiVersion: release-notes/v2 kind: feature area: traffic-management issue: - 48212 releaseNotes: - |
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Fri Jan 26 20:34:28 UTC 2024 - 207 bytes - Viewed (0) -
pkg/proxy/nftables/README.md
service IPs. (We *must* do this in `prerouting`, because the choice of endpoint IP may affect whether the packet then gets routed along the input path or the forward path.) - We do the DNAT for outbound traffic in `output`: this covers traffic coming from host-network processes to all types of service IPs. Regardless of the final destination, the traffic will take the "output path". (In the case where a
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Sun Jan 21 14:37:56 UTC 2024 - 5.9K bytes - Viewed (0) -
releasenotes/notes/failover-priority-lb.yaml
apiVersion: release-notes/v2 kind: feature area: traffic-management releaseNotes: - |
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Aug 25 06:49:06 UTC 2021 - 258 bytes - Viewed (0) -
releasenotes/notes/49700.yaml
understand. Under the old waypoint logic all types of traffic, both addressed to a service as well as addressed to a workload, were treated similarly because there wasn't a good way to properly associate a waypoint to a service. With the new attachment this limitation has been resolved. This includes adding a distinction between service addressed and workload addressed traffic. Annotating a service, or service-like kind, will redirect traffic which is service addressed to your waypoint. Likewise...
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed May 08 01:04:50 UTC 2024 - 2.9K bytes - Viewed (0) -
samples/helloworld/gateway-api/README.md
# Configure helloworld using the Kubernetes Gateway API Istio intends to make the Kubernetes [Gateway API](https://gateway-api.sigs.k8s.io/) the default API for traffic management [in the future](https://istio.io/latest/blog/2022/gateway-api-beta/). You can use the following instructions to configure the ingress gateway and routing for the helloworld sample. ## Before you begin
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Thu Sep 15 22:24:09 UTC 2022 - 2.4K bytes - Viewed (0) -
releasenotes/notes/36422.yaml
apiVersion: release-notes/v2 kind: feature area: traffic-management issue: - 29359 releaseNotes: - | **Added** support for hostname-based multi-network gateways for east-west traffic. The hostname will be resolved in the control plane and each of the IPs will be used as an endpoint. This behaviour can be disabled by setting
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Jan 11 19:28:24 UTC 2022 - 378 bytes - Viewed (0) -
releasenotes/notes/41018.yaml
apiVersion: release-notes/v2 kind: feature area: traffic-management issue: - 40919 releaseNotes: - | **Added** Allow creating inbound listeners for service ports and sidecar and ingress listener both using environment variable PILOT_ALLOW_SIDECAR_SERVICE_INBOUND_LISTENER_MERGE. This way traffic for service port is not sent via pass-through tcp even though its regular http traffic when sidecar ingress listener is defined.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Oct 17 15:54:10 UTC 2022 - 565 bytes - Viewed (0) -
releasenotes/notes/ignore-port.yaml
apiVersion: release-notes/v2 kind: bug-fix area: traffic-management issues: - 40474 releaseNotes: - | **Fixed** an issue causing traffic to not match (and return a `404`) when using wildcard domain names and including an unexpected port in the `Host` header. - | **Fixed** an issue causing traffic to match an unexpected route when using wildcard domain names and including an port in the `Host` header. - |
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Aug 17 16:29:11 UTC 2022 - 581 bytes - Viewed (0) -
releasenotes/notes/external-name.yaml
service, and traffic matching the service was sent to the configured DNS name. This caused a few issues: * Ports are required in Istio, but not in Kubernetes. This can result in broken traffic if ports are not configured as Istio expects, despite them working without Istio.
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Fri Oct 27 03:08:29 UTC 2023 - 2.7K bytes - Viewed (0)