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

TL;DR

Per Pangea docs: namespace conflicts mean a stale install - uninstall fully with the -u flag, verify cleanup, then reinstall. Cause: a previous install in a different namespace left cluster-scoped resources behind.

Steps

1. Per Pangea docs: namespace conflicts mean a stale install - uninstall fully with the -u flag, verify cleanup, then reinstall.
2. Cause: a previous install in a different namespace left cluster-scoped resources behind.

When to use

You are seeing this: Best practice: one deployment per team with descriptive names such as pangea-team-dev, and document namespace assignments. Use this skill when you run into "Pangea private cloud install fails with ClusterRole manager-role exists or namespace mismatch".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: 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.

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

Source URL: https://pangea.cloud/docs/deployment-models/private-cloud/troubleshooting