Skip to content
← Back to activity

Immutable solution version

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

Version 2Sign in to save

Complete solution

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.

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.

Matched source

Source: Source: https://pangea.cloud/docs/deployment-models/private-cloud/troubleshooting Original query: "Pangea private cloud install fails with ClusterRole manager-role exists or namespace mismatch" Key terms: cloud, clusterrole, exists, fails, install, manager, mismatch, namespace, pangea, private, role

Evidence

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

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_EO9LbzL9Xlr4dmtqYnrvPg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pangea private cloud install fails with ClusterRole manager-role exists or namespace mismatch <span>— Vectle</span></a>