Menu
On-prem Kubernetes cluster integration for running kubectl commands via Aurora agent relay or uploaded kubeconfig
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
GitHub code repository integration for investigating code changes, deployments, commits, PRs, and suggesting fixes during RCA
CloudBees CI integration for investigating builds, deployments, pipeline stages, and test results during RCA
CloudBees Operations Center integration for cross-controller deployment visibility and feature flag correlation during RCA
Bitbucket code repository integration for managing repos, branches, PRs, issues, and CI/CD pipelines
Fly.io integration for application monitoring, machine lifecycle management, metrics, logs, and incident remediation
Amazon CloudWatch alarm integration — receives alarm state-change notifications via SNS webhooks and creates incidents automatically
| name | kubectl_onprem |
| id | kubectl_onprem |
| description | On-prem Kubernetes cluster integration for running kubectl commands via Aurora agent relay or uploaded kubeconfig |
| category | infrastructure |
| connection_check | {"method":"is_connected_function","module":"chat.backend.agent.tools.kubectl_onprem_tool","function":"is_kubectl_onprem_connected"} |
| tools | ["get_connected_clusters","on_prem_kubectl"] |
| index | Infrastructure -- run kubectl on connected Kubernetes clusters (agent or kubeconfig) |
| rca_priority | 8 |
| allowed-tools | get_connected_clusters, on_prem_kubectl |
| metadata | {"author":"aurora","version":"1.0"} |
On-prem Kubernetes cluster integration for running kubectl commands on connected clusters. Commands are either relayed through the Aurora agent installed on the cluster, or executed directly using uploaded kubeconfig credentials.
IMPORTANT: Always call get_connected_clusters first to discover available clusters and their cluster_id before running any kubectl commands.
Note: For cloud-managed clusters (GCP GKE, AWS EKS, Azure AKS), use terminal_exec with kubectl commands instead.
Discover available on-prem clusters. Call this before using on_prem_kubectl.
Usage:
get_connected_clusters()
Returns cluster names, IDs, connection status, and metadata.
Run kubectl commands on connected on-prem Kubernetes clusters.
Usage:
on_prem_kubectl(cluster_id='CLUSTER_ID', command='get pods -n default')
Specify the cluster using the cluster_id returned by get_connected_clusters.
get_connected_clusters()on_prem_kubectl(cluster_id='ID', command='get pods -n NAMESPACE')on_prem_kubectl(cluster_id='ID', command='logs PODNAME -n NAMESPACE --tail=100')on_prem_kubectl(cluster_id='ID', command='describe pod PODNAME -n NAMESPACE')on_prem_kubectl(cluster_id='ID', command='get events -n NAMESPACE --sort-by=.lastTimestamp')on_prem_kubectl(cluster_id='ID', command='get nodes -o wide')on_prem_kubectl(cluster_id='ID', command='top pods -n NAMESPACE')cluster_id to target the correct cluster.terminal_exec with kubectl commands.