kubernetes-architect

Design Kubernetes platform architecture, GitOps workflows, and multi-cluster deployment strategies.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/bilacchi/agents-skills --skill kubernetes-architect-bilacchi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubernetes-architect
Source: https://github.com/bilacchi/agents-skills/tree/main/skills/kubernetes-architect
Command: npx skills add https://github.com/bilacchi/agents-skills --skill kubernetes-architect-bilacchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing production Kubernetes platforms involves complex decisions across cluster topology, GitOps tooling, security policies, service mesh, and cost optimization, and mistakes lead to fragile or expensive infrastructure. ## Core Features & Use Cases - Platform Architecture Design: Plan cluster topology, networking, multi-tenancy, and security boundaries across EKS, AKS, GKE, OpenShift, and self-managed clusters. - GitOps & Progressive Delivery: Implement ArgoCD, Flux, Argo Rollouts, and Flagger workflows following OpenGitOps principles with canary and blue/green strategies. - Security & Observability: Configure Pod Security Standards, OPA/Gatekeeper policies, service mesh, and Prometheus/Grafana/OpenTelemetry monitoring stacks. - Use Case: A platform team needs a multi-cluster Kubernetes setup with GitOps for a financial services company; the skill guides cluster design, ArgoCD repository structure, RBAC isolation, and disaster recovery planning. ## Quick Start Ask the assistant to design a multi-cluster Kubernetes platform with GitOps-based progressive delivery for your workloads.

Frequently Asked Questions about kubernetes-architect

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

FAQPage Schema
How do I design a multi-cluster Kubernetes architecture?▼

Start by gathering workload requirements, compliance needs, and scale targets, then define cluster topology, networking, and security boundaries. Use Cluster API or fleet management for multi-cluster operations and validate the design in staging before production rollout.

How to implement GitOps with ArgoCD or Flux?▼

Follow the OpenGitOps principles: store desired state declaratively in Git, use app-of-apps or environment promotion repository patterns, and let agents continuously reconcile actual state. Add progressive delivery with Argo Rollouts or Flagger for canary and blue/green deployments.

ArgoCD vs Flux for Kubernetes GitOps?▼

Both are supported GitOps tools covered by this skill. ArgoCD offers a rich UI and app-of-apps patterns, while Flux v2 provides a modular toolkit approach; the choice depends on your team's workflow and repository structure preferences.

Does this cover Kubernetes security and policy enforcement?▼

Yes, it covers Pod Security Standards, network policies, RBAC design, OPA/Gatekeeper and Kyverno policy as code, runtime security with Falco, and supply chain security with Sigstore and SLSA. Policy changes should be tested in staging first.

When should I not use a Kubernetes architecture skill?▼

Avoid it for local dev clusters, single-node setups, or application-level troubleshooting without platform changes. It targets platform-scale design decisions, not debugging application code or non-containerized workloads.