Conformance Validation

Nobody has claimed this yet.

## What problem are you trying to solve?

`check` does a great job of validating the health of the control plane and making sure that an install happened. Unfortunately, `check` is limited to only reading from the cluster and not running any actual workloads. This makes it challenging to know whether interactions between the control plane and data plane are working successfully.

## How should the problem be solved?

Create a new tool that adds sample workloads to the cluster and runs something similar to integration tests against the installation. This will test things such as injection, policies and load limits for the cluster itself.

An example of conformance validation for kubernetes is: [Sonobuoy](https://github.com/vmware-tanzu/sonobuoy).

## Any alternatives you've considered?

It is possible to simply run through getting started today. This ends up exercising many of the same use cases. However, walking through getting started leaves much of the debugging and actual testing up to new users who might not know what they should be exercising. As an example, getting started does not currently test ingress, route based metrics or distributed tracing. All of these features could be exercised with a conformance testing suite.

## How would users interact with this feature?

There should be a new set of CLI commands that can start, monitor and report on conformance testing.

Review the existing `check` command and getting started flow first; the issue does not name implementation files or tests. Define CLI commands for starting, monitoring, and reporting, then cover workloads and interactions including injection, policies, load limits, ingress, route-based metrics, and distributed tracing.

Written by the indexing model from the issue text.