Comment 6 for bug 1990279

For the history, one more time K8s charm deployed on LXD with confusing error:

> unit-mongodb-k8s-2: 10:55:03 ERROR juju.worker.uniter.operation hook "db-storage-attached" (via hook dispatching script: dispatch) failed: exit status 1

We need ability to hint users about incompatibility situation clearly.

Extra findings: the charm can work well on MicroK8s/GKE/... but can be temporary broken for Amazon EKS.
Would be great to release "revision" with a precise lock, e.g.:

> mysql-k8s-operator.git/metadata.yaml
>> assumes:
>> - k8s-api
>> - not EKS:
>> message: "Amazon EKS is temporary NOT supported by this revision:"
>> url: https://bugs.launchpad.net/juju/+bug/1990279
>> - not VM:
>> message: "It is K8s operator, consider to use VM operator for your needs:"
>> url: https://charmhub.io/mysql

The list of keywords can be easily brewed: K8s(MicrkoK8s, GKE, EKS, ...), VM(LXD, OpenStack), ...

Tnx!