- Sort Score
- Result 10 results
- Languages All
Results 61 - 70 of 1,007 for traffic (0.23 sec)
-
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) -
tests/integration/pilot/testdata/upgrade/1.6.11-install.yaml.tar
annotation .ObjectMeta `sidecar.istio.io/interceptionMode` .ProxyConfig.InterceptionMode }}" traffic.sidecar.istio.io/includeOutboundIPRan: "{{ annotation .ObjectMeta `traffic.sidecar.istio.io/includeOutboundIPRan` .Values.global.proxy.includeIPRanges }}" traffic.sidecar.istio.io/excludeOutboundIPRan: "{{ annotation .ObjectMeta `traffic.sidecar.istio.io/excludeOutboundIPRan` .Values.global.proxy.excludeIPRanges }}" traffic.sidecar.istio.io/includeInboundPorts: "{{ annotation .ObjectMeta `traffic.sidecar.i...
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Wed Jan 13 16:06:08 UTC 2021 - 50K 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) -
tests/integration/telemetry/policy/traffic_registry_only_test.go
}, }, { Name: "HTTPS Traffic", PortName: "https", Expected: Expected{ Query: prometheus.Query{ Metric: "istio_tcp_connections_closed_total", Aggregation: "sum", Labels: map[string]string{ "destination_service_name": "BlackHoleCluster", }, }, }, }, { Name: "HTTPS Traffic Conflict", PortName: "https-conflict",
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Oct 18 18:03:23 UTC 2022 - 3.3K bytes - Viewed (0) -
cluster/addons/calico-policy-controller/globalnetworkpolicy-crd.yaml
type: object spec: properties: applyOnForward: description: ApplyOnForward indicates to apply the rules in this policy on forward traffic. type: boolean doNotTrack: description: DoNotTrack indicates whether packets matched by the rules
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Fri May 07 20:48:43 UTC 2021 - 45.2K bytes - Viewed (0) -
staging/src/k8s.io/api/extensions/v1beta1/types_swagger_doc_generated.go
"to": "List of destinations for outgoing traffic of pods selected for this rule. Items in this list are combined using a logical OR operation. If this field is empty or missing, this rule matches all destinations (traffic not restricted by destination). If this field is present and contains at least one item, this rule allows traffic only if the traffic matches at least one item in the to list.",...
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Mon May 01 18:19:25 UTC 2023 - 42.5K bytes - Viewed (0) -
releasenotes/notes/add-idle-timeout-to-destination-rule-tcp-settings.yaml
apiVersion: release-notes/v2 kind: feature area: traffic-management issue: [] releaseNotes: - |
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Tue Dec 19 15:18:18 UTC 2023 - 189 bytes - Viewed (0) -
releasenotes/notes/external-name-on.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: Thu Nov 02 18:58:52 UTC 2023 - 2.4K bytes - Viewed (0) -
releasenotes/notes/max-concurrent-streams.yaml
apiVersion: release-notes/v2 kind: feature area: traffic-management releaseNotes: - |
Registered: Fri Jun 14 15:00:06 UTC 2024 - Last Modified: Mon Jan 08 21:39:29 UTC 2024 - 210 bytes - Viewed (0)