ACCESSING CLUSTERS

SkillCloud & infra

Kubernetes operational knowledge for accessing clusters, running kubectl, understanding Flux status, and navigating the homelab Kubernetes environment.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the ACCESSING CLUSTERS skill

What this skill tells your AI

The instructions your AI receives, as published by ionfury/homelab in .claude/skills/k8s/SKILL.md and read by ahel’s review.

The available clusters are dev, integration, and live. Use the coresponding kube context for access.

Common kubectl Patterns

CommandPurpose
kubectl get pods -n <ns>List pods in a namespace
kubectl get pods -AList pods across all namespaces
kubectl describe pod <pod> -n <ns>Detailed pod info with events
kubectl logs <pod> -n <ns> --tail=100Recent logs from a pod
kubectl logs <pod> -n <ns> --previousLogs from previous container instance
kubectl get events -n <ns> --sort-by='.lastTimestamp'Recent events timeline
kubectl top pods -n <ns>CPU/memory usage per pod
kubectl top nodesCPU/memory usage per node
kubectl get ns <ns> --show-labelsNamespace labels (network policy profiles)
kubectl explain <resource>API schema reference for a resource type

Flux GitOps Commands

# Check status
flux --context <cluster> get all
flux --context <cluster> get kustomizations
flux --context <cluster> get helmreleases -A

# Trigger reconciliation
flux --context <cluster> reconcile source git flux-system
flux --context <cluster> reconcile kustomization <name>
flux --context <cluster> reconcile helmrelease <name> -n <namespace>

Flux Status Interpretation

StatusMeaningAction
Ready: TrueReconciled and healthyNone
Ready: FalseFailed to reconcileCheck the message/reason
Stalled: TrueStopped retrying after repeated failuresSuspend/resume to reset (see sre skill)
Suspended: TrueIntentionally pausedResume: flux resume <type> <name>
ReconcilingActively being appliedWait for completion

Researching Unfamiliar Services

When investigating unknown services, spawn a haiku agent to research documentation:

Task tool:
- subagent_type: "general-purpose"
- model: "haiku"
- prompt: "Research [service] troubleshooting docs. Focus on:
  1. Common failure modes
  2. Health indicators
  3. Configuration gotchas
  Start with: [docs-url]"

Chart URL to Docs mapping:

Chart SourceDocumentation
charts.jetstack.iocert-manager.io/docs
charts.longhorn.iolonghorn.io/docs
grafana.github.iografana.com/docs
prometheus-community.github.ioprometheus.io/docs

Common Confusions

BAD: Use helm list to check Helm release status GOOD: Use kubectl get helmrelease -A — Flux manages releases via CRDs, not Helm CLI

Signals

GitHub stars
25
Forks
3
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
k8s
Source
github.com/ionfury/homelab