The bin/test-cleanup script does not delete linkerd extensions which have been installed on the cluster. This can cause subsequent test runs to fail when those extensions are installed again.

The script should be updated to full delete all linkerd extensions. It can use the linkerd.io/extension label to locate all resources associated with an extension. This label may need to be added to

In lieu of #283, implement Stackdriver Canary Analysis for use in GKE.

Current Behavior
The individual service mesh management pages have a namespace field with "default" prepopulated.

Desired Behavior
The namespace field should not only show "default" as an option, but should also include the list of namespaces that are currently present in the user's Kubernetes environment. Pre-populating this text field will be a UX improvement and it will also help

Current Behavior
This page should have the SMI and Meshery logos on it - https://layer5.io/projects/service-mesh-interface

Contributor Resources
The layer5 repo contains two websites. The current generation and the next-generation of the layer5.io site.

If the layer5-ng label is absent on this issue, then this issue pertains to the current generation of the layer5.io websi

What's in https://linkerd.io/2/reference/architecture/ does not reflect 2.3.