New Features
- Capture all external address information on the Destination CRD so that any externally-addressable Kubernetes Service can be used as an ingress gateway. (#1611)
- Mark as deprecated the
IngressGatewayDetectorin Settings, which is no longer needed now that external address information is colocated in the relevant Destination. (#1611) - Add a
meshctl cluster configurecommand that interactively allows the user to generate a file that is referenced in subsequent meshctl commands which automate cluster interaction. (#1584) - Add a
meshctl cluster listcommand that allows the user to list all the registered clusters. (#1584) - Add a
meshctl debug reportcommand that selectively captures cluster information and logs into an archive to help diagnose problems. (https://github.com/solo-io/gloo-mesh-enterprise/issues/581) - Update
meshctl uninstallto delete all Gloo Mesh management plane CRDs. (#1644)
Fixes
- Discover externally addressable Kubernetes Services from any namespace, any of which can act as an ingress gateway. (https://github.com/solo-io/gloo-mesh-enterprise/issues/664)
- In the destination federation translator, gracefully handle case when Istio mesh has no ingress gateway. (#1630)
- Fix VirtualMesh link in traffic policy doc. (#1385)
- Fix TrafficPolicySpec link in traffic policy doc. (#1540)
- Modify the
meshctl checkcommand such that we are reporting the number of connected pull and push agents instead of checking that it is a number. (#1562)