rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "meshery-metrics-reader" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "meshery-operator"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "meshery" app=meshery code=2155 probable-cause="Kubernetes cluster might not be connected.Leftover resources from partial install" severity=2 short-description="Error occurred while applying Helm Chart" suggested-remediation="Try reinstalling.Try reconnecting your kubernetes cluster.Clean up artifacts from preinstalled helm release manually"
@manav_kapoor This is because when the Meshery server tries to deploy the operator charts, it conflicts with the previous installation of Meshery which was not cleaned up properly.
You can remove any orphaned artefacts from the cluster and try this again and it should work.
You can first delete the CRDs by running kubectl delete crd <crd name>.
You can find the CRDs by running kubectl get crds.
Then you can remove the namespace “meshery” completely by running kubectl delete namespace meshery.
mesheryctl would handle this when users are running it. But for a dev environment, this might be needed. There is an open issue in mesheryctl to handle such cases of orphaned artefacts as well.
