apiVersion: release-notes/v2
kind: feature
area: documentation
releaseNotes:
  - |
    **Added** The locality load balancing docs have been re-written into a
    formal traffic management task. The new docs describe in more detail
    how locality load balancing works as well as how to configure both
    failover and weighted distribution. In addition, the new docs are now

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

releaseNotes:
- |

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

apiVersion: release-notes/v2
kind: bug-fix
area: networking
issue:
- 23494
releaseNotes:
- |

kind: feature
area: traffic-management
releaseNotes:
- |

// GRPC proposal:
// https://github.com/grpc/proposal/blob/master/A27-xds-global-load-balancing.md
//
// Note that this implementation is tested against gRPC, but it is generic - any other framework can
// use this XDS mode to get load balancing info from Istio, including MC/VM/etc.

// The corresponding RDS response is also generated - currently gRPC has special differences

kind: feature
area: networking
issue:
  - 28798

releaseNotes:
- |
  **Fixed** When using PeerAuthentication to turn off mTLS while using multi-network, non-mtls endpoints will be

    onboarding flow uses a simpler configuration which allows services across
    the mesh to be accessed via `*.cluster.local`. There were several
    limitations with `.global`, such as poor load balancing when using
    gateways, which are no longer an issue with the new configuration.

upgradeNotes:
  - title: Multicluster `.global` Stub Domain Deprecation
    content: |

  command: server http://minio{1...4}/data{1...3}
  env_file:
    - ./minio.env
  expose:
    - "9000"
    - "9001"

# starts 4 docker containers running minio server instances.
# using nginx reverse proxy, load balancing, you can access
# it through port 9000.
services:
  minio1:
    <<: *minio-common
    hostname: minio1
    volumes:
      - data1-1:/data1
      - data1-2:/data2
      - data1-3:/data3

  minio2:

  command: server http://site2-minio{1...4}/data{1...2}
  environment:
    - MINIO_PROMETHEUS_AUTH_TYPE=public
    - CI=true

# starts 4 docker containers running minio server instances.
# using nginx reverse proxy, load balancing, you can access
# it through port 9000.
services:
  site2-minio1:
    <<: *minio-common
    hostname: site2-minio1
    volumes:
      - site2-data1-1:/data1
      - site2-data1-2:/data2

  site2-minio2: