一键导入
dot-ai-port-destroy
// Remove all Port integrations, Kubernetes resources, and local files created by /port-setup
// Remove all Port integrations, Kubernetes resources, and local files created by /port-setup
| name | dot-ai-port-destroy |
| description | Remove all Port integrations, Kubernetes resources, and local files created by /port-setup |
| user-invocable | true |
Remove all Port integrations, Kubernetes resources, and local files created by /port-setup.
Check the following and instruct the user to install/configure if missing:
PORT_CLIENT_IDPORT_CLIENT_SECRETBefore destroying, discover what exists and how it was deployed:
argocd namespace) or Flux (flux-system namespace)apps/port-*.yaml).github/workflows/port-*.yaml) and repository secretsIMPORTANT: When ArgoCD or Flux is detected, deletions must go through Git first.
This order ensures the exporter stops syncing before you delete resources in Port.
Critical: Delete the K8s exporter FIRST to stop new entities from being synced to Port.
Check deployment method and delete accordingly:
With ArgoCD/Flux (GitOps):
rm <manifest-dir>/port-k8s-exporter.yaml
git add -A && git commit -m "Remove port-k8s-exporter" && git push
kubectl get ns port-k8s-exporter should return not foundkubectl delete ns port-k8s-exporterWith Helm directly (non-GitOps):
helm uninstall port-k8s-exporter -n port-k8s-exporter
kubectl delete secret port-credentials -n port-k8s-exporter
kubectl delete externalsecret port-credentials -n port-k8s-exporter # if using ESO
kubectl delete namespace port-k8s-exporter
Delete all self-service actions created for CRDs. Do this BEFORE deleting blueprints since actions reference blueprints.
mcp__port-vscode-eu__list_actions to find actions with identifiers matching patterns:
create_*, update_*, delete_*mcp__port-vscode-eu__delete_actionDelete the blueprints created during setup from the Data Model page.
Steps:
mcp__port-vscode-eu__list_blueprints to discover which blueprints exist/port-setup (exclude system blueprints starting with _ and the defaults: cluster, namespace, workload)STOP and wait for user confirmation before proceeding.
Look for Port-related workflows and delete them:
rm .github/workflows/port-*.yaml
gh secret delete PORT_CLIENT_ID
gh secret delete PORT_CLIENT_SECRET
gh secret delete KUBE_CONFIG # if created
Commit and push the deletions:
git add -A && git commit -m "Remove Port self-service workflows" && git push
If user wants to remove GitHub integration:
After cleanup, verify:
kubectl get ns port-k8s-exporter returns not foundCreate changelog fragment for release notes. Invoke during /prd-done workflow during the first push to the PR.
Generate intelligent CI/CD workflows through interactive conversation by analyzing repository structure and user preferences
Generate production-ready, secure, multi-stage Dockerfile and .dockerignore for any project
Manage the knowledge base: ingest documents, search with natural language, or delete chunks. Use "ingest" to store organizational documentation, "search" to find relevant content semantically, or "deleteByUri" to remove all chunks for a document. TIP: For complex questions, you can call search multiple times with different phrasings to gather comprehensive information before synthesizing your answer.
Unified tool for managing cluster data: organizational patterns, policy intents, and resource capabilities. For patterns and policies: supports create, list, get, delete, deleteAll, and search operations (patterns also support step-by-step creation workflow). For capabilities: supports scan, list, get, delete, deleteAll, and progress operations for cluster resource capability discovery and management. Use dataType parameter to specify what to manage: "pattern" for organizational patterns, "policy" for policy intents, "capabilities" for resource capabilities.
AI-powered Kubernetes application operations tool for Day 2 operations. Handles updates, scaling, enhancements, rollbacks, and deletions through natural language intents. Analyzes current state, applies organizational patterns and policies, validates changes via dry-run, and executes approved operations safely.