issue:
  - 45415

releaseNotes:
  - |
    **Fixed** a bug where overlapping wildcard hosts in a VirtualService would produce incorrect routing configuration when wildcard services were selected (e.g. in ServiceEntries).

upgradeNotes:
  - title: Overlapping Wildcard Conflicts
    content: |
      This fix changes the behavior of overlapping wildcard hosts in VirtualService. Previously, the oldest VirtualService would take precedence

	_ interface{int | int /* ERROR "overlapping terms int and int" */ }
	_ interface{int | ~ /* ERROR "overlapping terms ~int and int" */ int}
	_ interface{~int | int /* ERROR "overlapping terms int and ~int" */ }
	_ interface{~int | ~ /* ERROR "overlapping terms ~int and ~int" */ int}

	_ interface{T1 | bool | string | T1 | bool /* ERROR "overlapping terms bool and bool" */ | string /* ERROR "overlapping terms string and string" */ }

	union interface{int|~string}

	// Union terms must describe disjoint (non-overlapping) type sets.
	_ interface{int|int /* ERROR "overlapping terms int" */ }
	_ interface{int|~ /* ERROR "overlapping terms ~int" */ int }
	_ interface{~int|~ /* ERROR "overlapping terms ~int" */ int }
	_ interface{~int|MyInt /* ERROR "overlapping terms p.MyInt and ~int" */ }
	_ interface{int|any}
	_ interface{int|~string|union}

      method:
        exact: GET
    route:
    - destination:
        host: sample.foo.svc.cluster.local
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: overlapping-in-single-match
spec:
  hosts:
  - sample.baz.svc.cluster.local
  http:
  - name: "send product to sample.foo"
    match:
    - uri:
        prefix: "/api/v1/product"
      method:
        exact: GET

     */
    boolean isSuccessful();

    /**
     * Snapshots of the roots of output properties.
     *
     * In the presence of overlapping outputs this might be different from
     * {@link BeforeExecutionState#getOutputFileLocationSnapshots()},
     * as this does not include overlapping outputs not produced by the work.
     */
    ImmutableSortedMap<String, FileSystemSnapshot> getOutputFilesProducedByWork();

    /**

---
apiVersion: telemetry.istio.io/v1alpha1
kind: Telemetry
metadata:
  name: overlap-1
  namespace: default
spec:
  selector:
    matchLabels:
      app: ratings-app # Multiple telemetries select overlapping workloads, should generate errors for both
  metrics:
    - providers:
        - name: prometheus
      overrides:
        - match:
            metric: ALL_METRICS
          disabled: false
---

	dstBase := dd.wrPos
	dstPos := dstBase
	srcPos := dstPos - dist
	endPos := dstPos + length
	if endPos > len(dd.hist) {
		endPos = len(dd.hist)
	}

	// Copy non-overlapping section after destination position.
	//
	// This section is non-overlapping in that the copy length for this section
	// is always less than or equal to the backwards distance. This can occur
	// if a distance refers to data that wraps-around in the buffer.

apiVersion: release-notes/v2
kind: feature
area: bug-fix
issue:
- 29199

releaseNotes:
- |
  **Fixed** a regression in Istio 1.8.0 causing workloads with multiple Services with overlapping ports to send

	~rune
}

// Type sets may contain each type at most once.
type _ interface {
	~int|~ /* ERROR "overlapping terms ~int" */ int
	~int|int /* ERROR "overlapping terms int" */
	int|int /* ERROR "overlapping terms int" */
}

type _ interface {
	~struct{f int} | ~struct{g int} | ~ /* ERROR "overlapping terms" */ struct{f int}
}

// Interface term lists can contain any type, incl. *Named types.

    labels:
      app: ratings-app # Multiple sidecars select overlapping workloads, should generate errors for both
  egress:
  - hosts:
    - "./*"
---
apiVersion: networking.istio.io/v1alpha3
kind: Sidecar
metadata:
  name: overlap-2
  namespace: default
spec:
  workloadSelector:
    labels:
      myapp: ratings-myapp # Multiple sidecars select overlapping workloads, should generate errors for both
  egress: