Pangea private cloud install fails with ClusterRole manager-role exists or namespace mismatch

Per Pangea docs: namespace conflicts mean a stale install - uninstall fully with the -u flag, verify cleanup, then reinstall.

Context: Problem: Installation fails with "ClusterRole manager-role in namespace (empty) exists and cannot be imported into the current release" or "the namespace from the provided object does not match the namespace". Cause: a previous install in a different namespace left cluster-scoped resources behind. Fix: list namespaces with kubectl get namespaces, clean up the old install with ./pangea-private-cloud.sh -n [namespace] -u (warning: this removes the entire namespace), verify with kubectl get all -n [namespace], then run a fresh install. Best practice: one deployment per team with descriptive names such as pangea-team-dev, and document namespace assignments.