with one click
namespace-troubleshooting
// Troubleshoot namespace stuck in Terminating state, ResourceQuota exhaustion, or RBAC permission denied errors. Use when resources cannot be created or forbidden errors occur.
// Troubleshoot namespace stuck in Terminating state, ResourceQuota exhaustion, or RBAC permission denied errors. Use when resources cannot be created or forbidden errors occur.
Resolve a CVE vulnerability issue from Jira. Reads the CVE details, assesses impact, and either marks "not affected" with a Jira comment and transition, bumps the affected dependency, or implements a code fix. Use when the user says "cve", "resolve CVE", or provides a CVE Jira issue.
Assess whether an application is ready to migrate to OpenShift. Use when the user describes an application and asks about migration, containerization, or moving to Kubernetes/OpenShift.
Triage production incidents involving data corruption, data loss, slow performance, or outages. Classify severity and recommend immediate actions.
Update Python dependencies to latest versions using uv, regenerate lock and requirements.txt, then verify linting and tests pass. Fix breakage from API changes in bumped packages. Use when the user says "deps update", "bump dependencies", or "update deps".
Review PR with structured approach covering architecture, naming, patterns, and critical questions
Troubleshoot ClusterOperator in Degraded, Unavailable, or not Progressing state. Use when operator status shows error conditions, reconciliation failures, or degraded health checks.
| name | namespace-troubleshooting |
| description | Troubleshoot namespace stuck in Terminating state, ResourceQuota exhaustion, or RBAC permission denied errors. Use when resources cannot be created or forbidden errors occur. |
When a user reports issues at the namespace/project level — stuck deletion, inability to create resources, or permission errors — follow this structured approach to identify the specific blocker and provide a targeted fix.
Start by confirming the namespace exists and its phase:
If the namespace is stuck in Terminating state:
metadata.finalizers — these are the hooks preventing deletion.terminationGracePeriodSeconds or are stuck in pre-stop hooks.Never suggest blanket removal of namespace finalizers ("just patch the namespace to remove all finalizers"). This skips all cleanup and leaks resources. Always identify and address the specific blocking resources first.
If deployments or pods fail to create with quota-related errors:
Always show the numbers. "Quota exceeded" without showing the actual usage vs. limit is not actionable.
If pod creation fails with LimitRange-related errors:
If the user gets Forbidden errors when operating in the namespace:
Always specify the exact verb+resource the user is missing (e.g., "create deployments.apps") rather than vaguely saying "insufficient permissions."
OpenShift Projects are namespaces with additional metadata. If the issue involves Projects specifically:
self-provisioner ClusterRoleBinding — removal of this binding prevents users from creating their own Projects.