Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

kubectl-cli

Sterne1

Forks1

Aktualisiert7. Mai 2026 um 12:34

Kubernetes CLI operations for AKS cluster management. USE FOR: kubectl get, kubectl apply, kubectl describe, pod troubleshooting, service debugging, namespace management. DO NOT USE FOR: Helm charts (use helm-cli), ArgoCD sync (use argocd-cli), Azure resource provisioning (use azure-cli).

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Ohorizons

Ohorizons/open-horizons-platform

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Netzwerk- und ComputersystemadministratorenInformatik- und Mathematikberufe·SOC 15-1244

SKILL.md

readonly

name	kubectl-cli
description	Kubernetes CLI operations for AKS cluster management. USE FOR: kubectl get, kubectl apply, kubectl describe, pod troubleshooting, service debugging, namespace management. DO NOT USE FOR: Helm charts (use helm-cli), ArgoCD sync (use argocd-cli), Azure resource provisioning (use azure-cli).

When to Use

Cluster health verification
Resource deployment and management
Troubleshooting pod issues
Viewing logs and events

Prerequisites

kubectl installed and configured
KUBECONFIG set to valid config
kubelogin for Azure AD authentication
Appropriate RBAC permissions

Commands

Cluster Health

# Cluster info
kubectl cluster-info

# Node status
kubectl get nodes -o wide

# System pods
kubectl get pods -n kube-system

# Unhealthy pods across all namespaces
kubectl get pods -A --field-selector=status.phase!=Running,status.phase!=Succeeded

Resource Management

# Dry-run before apply
kubectl apply -f manifest.yaml --dry-run=client -o yaml

# Diff changes
kubectl diff -f manifest.yaml

# Apply with recording
kubectl apply -f manifest.yaml --record

# Delete with grace
kubectl delete -f manifest.yaml --grace-period=30

Troubleshooting

# Describe pod
kubectl describe pod <pod-name> -n <namespace>

# Pod logs (current)
kubectl logs -f <pod-name> -n <namespace>

# Pod logs (previous crash)
kubectl logs <pod-name> -n <namespace> --previous

# Events by time
kubectl get events -n <namespace> --sort-by='.lastTimestamp'

# Exec into pod
kubectl exec -it <pod-name> -n <namespace> -- /bin/sh

Resource Queries

# Get all resources in namespace
kubectl get all -n <namespace> -o wide

# Get resource as YAML
kubectl get deployment <name> -n <namespace> -o yaml

# Resource usage
kubectl top pods -n <namespace>
kubectl top nodes

Best Practices

ALWAYS use --dry-run=client before apply
ALWAYS specify namespace with -n
Use labels for selection: -l app=myapp
Check events when pods fail
Use kubectl diff for change preview
NEVER delete without explicit namespace

Output Format

Command executed
Resource status summary
Any warnings or errors
Recommended actions

Integration with Agents

Used by: @platform, @devops, @sre, @test

Mehr aus diesem Repository

gleiches Repository

ai-foundry-operations

Ohorizons/open-horizons-platform

Azure AI Foundry — provisioning, model deployment, RAG configuration, and operational management. USE FOR: provision AI Foundry, deploy AI model, configure RAG, AI Foundry operations, OpenAI model deployment, AI workspace setup. DO NOT USE FOR: general Azure infrastructure (use azure-infrastructure), Terraform IaC (use terraform-cli), Kubernetes operations (use kubectl-cli).

2026-05-071

argocd-cli

Ohorizons/open-horizons-platform

ArgoCD CLI operations for GitOps workflows — installation, bootstrap, and day-2 management. USE FOR: ArgoCD install, ArgoCD bootstrap, GitOps sync, ArgoCD app create, ArgoCD troubleshoot, ApplicationSet. DO NOT USE FOR: Helm chart management (use helm-cli), kubectl operations (use kubectl-cli), CI/CD pipeline creation (use @devops).

2026-05-071

azure-cli

Ohorizons/open-horizons-platform

Azure CLI operations for cloud resource management. USE FOR: az login, az aks, az acr, az keyvault, Azure resource provisioning, Azure resource group, Azure subscription management. DO NOT USE FOR: Terraform IaC (use terraform-cli), Kubernetes operations (use kubectl-cli), Helm charts (use helm-cli).

2026-05-071

azure-infrastructure

Ohorizons/open-horizons-platform

Azure infrastructure patterns and best practices. USE FOR: Azure architecture patterns, hub-spoke networking, private endpoints, Workload Identity, resource naming, tagging strategy. DO NOT USE FOR: Terraform CLI commands (use terraform-cli), Azure CLI commands (use azure-cli), Kubernetes operations (use kubectl-cli).

2026-05-071

backstage-deployment

Ohorizons/open-horizons-platform

Deploys the upstream open-source Backstage developer portal on Azure AKS or locally via Docker Desktop. USE FOR: deploy Backstage, Backstage on AKS, Backstage local Docker, Backstage Helm chart, Backstage PostgreSQL, Backstage ACR image, Backstage GitHub OAuth. DO NOT USE FOR: Backstage plugin development (use @platform), Golden Path template creation (use @platform), Azure infrastructure provisioning (use @azure-portal-deploy).

2026-05-071

codespaces-golden-paths

Ohorizons/open-horizons-platform

Configures GitHub Codespaces dev environments for each Golden Path template type so developers get a fully ready workspace when scaffolding from the portal. USE FOR: devcontainer.json configuration, Codespaces setup, Golden Path dev environment, container features, SDK pre-installation. DO NOT USE FOR: Backstage deployment (use backstage-deployment), CI/CD pipelines (use @devops), template creation (use @platform).

2026-05-071

name	kubectl-cli
description	Kubernetes CLI operations for AKS cluster management. USE FOR: kubectl get, kubectl apply, kubectl describe, pod troubleshooting, service debugging, namespace management. DO NOT USE FOR: Helm charts (use helm-cli), ArgoCD sync (use argocd-cli), Azure resource provisioning (use azure-cli).

When to Use

Cluster health verification
Resource deployment and management
Troubleshooting pod issues
Viewing logs and events

Prerequisites

kubectl installed and configured
KUBECONFIG set to valid config
kubelogin for Azure AD authentication
Appropriate RBAC permissions

Commands

Cluster Health

# Cluster info
kubectl cluster-info

# Node status
kubectl get nodes -o wide

# System pods
kubectl get pods -n kube-system

# Unhealthy pods across all namespaces
kubectl get pods -A --field-selector=status.phase!=Running,status.phase!=Succeeded

Resource Management

# Dry-run before apply
kubectl apply -f manifest.yaml --dry-run=client -o yaml

# Diff changes
kubectl diff -f manifest.yaml

# Apply with recording
kubectl apply -f manifest.yaml --record

# Delete with grace
kubectl delete -f manifest.yaml --grace-period=30

Troubleshooting

# Describe pod
kubectl describe pod <pod-name> -n <namespace>

# Pod logs (current)
kubectl logs -f <pod-name> -n <namespace>

# Pod logs (previous crash)
kubectl logs <pod-name> -n <namespace> --previous

# Events by time
kubectl get events -n <namespace> --sort-by='.lastTimestamp'

# Exec into pod
kubectl exec -it <pod-name> -n <namespace> -- /bin/sh

Resource Queries

# Get all resources in namespace
kubectl get all -n <namespace> -o wide

# Get resource as YAML
kubectl get deployment <name> -n <namespace> -o yaml

# Resource usage
kubectl top pods -n <namespace>
kubectl top nodes

Best Practices

ALWAYS use --dry-run=client before apply
ALWAYS specify namespace with -n
Use labels for selection: -l app=myapp
Check events when pods fail
Use kubectl diff for change preview
NEVER delete without explicit namespace

Output Format

Command executed
Resource status summary
Any warnings or errors
Recommended actions

Integration with Agents

Used by: @platform, @devops, @sre, @test