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...

# 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

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

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.

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.
- |

      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.

			},
		},
		{
			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",

apiVersion: release-notes/v2
kind: feature
area: traffic-management
issue: []
releaseNotes:
  - |

      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.

apiVersion: release-notes/v2
kind: feature
area: traffic-management
releaseNotes:
- |