k8s

Diagnose Kubernetes clusters and Flux GitOps reconciliation with kubectl commands.

1|Updated Apr 6, 2025

Search Tags:#troubleshooting #kubernetes #gitops #kubectl #helmrelease #flux-cd #internal-service-urls

Ready to run

npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill k8s-david-driscoll

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: k8s
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/k8s
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill k8s-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the time and guesswork required to access Kubernetes clusters, run correct kubectl checks, and interpret Flux GitOps reconciliation state when troubleshooting homelab workloads.

Core Features & Use Cases

Cluster access & kubectl command patterns: Helps you run reliable commands for pods, namespaces, events, logs, and resource explanations using the proper cluster context.
Flux reconciliation & status interpretation: Guides you through checking kustomizations and HelmReleases and triggering reconciliation or understanding conditions like Ready, Stalled, and Suspended.
Service discovery via internal URLs: Helps you find the right internal service endpoints and understand OAuth2 Proxy limitations for API access.

Quick Start

Ask: "Using the live cluster context, how do I check whether Prometheus is healthy and confirm Flux reconciliation status, including the commands to view relevant events and logs?"

Frequently Asked Questions about k8s

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check Flux GitOps reconciliation status for a HelmRelease or kustomization?▼

To check Flux GitOps reconciliation status, use the Flux CLI to inspect kustomization and HelmRelease conditions like Ready, Stalled, or Suspended. You can trigger reconciliation actions to force sync and verify healthy states.

What is the correct way to run kubectl checks for pod health in a specific cluster context?▼

Running kubectl checks for pod health requires setting the correct cluster context first. You can then execute commands to view pods, namespaces, events, and logs to validate workload health and troubleshoot issues accurately.

Why should I avoid using the Helm CLI for Flux-managed HelmRelease resources?▼

You should avoid the Helm CLI for Flux-managed HelmRelease resources because it creates anti-patterns. Flux GitOps manages the lifecycle, so using Helm CLI directly can desync state and break reconciliation tracking.

How do I find internal service URLs for API or browser access in Kubernetes?▼

Finding internal service URLs in Kubernetes involves querying service endpoints using kubectl. This helps locate internal service addresses, though you need to understand OAuth2 Proxy limitations that might restrict direct API access.

Can I use Flux CLI commands to troubleshoot stalled GitOps deployments?▼

Yes, you can use Flux CLI commands to troubleshoot stalled GitOps deployments by interpreting condition semantics. The CLI reveals Stalled conditions and event logs, enabling you to diagnose and trigger manual reconciliation.