スキル gitops-workflow
📦

gitops-workflow

低リスク ⚙️ 外部コマンド🌐 ネットワークアクセス

Implement GitOps workflows with ArgoCD and Flux

こちらからも入手できます: wshobson

Managing Kubernetes deployments manually leads to configuration drift and inconsistent environments. This skill enables automated, declarative deployments using Git as the single source of truth with continuous reconciliation.

対応: Claude Codex Code(CC)
🥉 72 ブロンズ
1

スキルZIPをダウンロード

2

Claudeでアップロード

設定 → 機能 → スキル → スキルをアップロードへ移動

3

オンにして利用開始

テストする

「gitops-workflow」を使用しています。 Set up ArgoCD for a new Kubernetes cluster

期待される結果:

Complete installation guide with kubectl commands for namespace creation, manifest application, initial password retrieval, and CLI configuration steps.

「gitops-workflow」を使用しています。 Create a GitOps application manifest for production

期待される結果:

ArgoCD Application YAML with source repository reference, target path, destination cluster, sync policy with prune and self-heal enabled, and namespace creation option.

「gitops-workflow」を使用しています。 Implement secret management without storing secrets in Git

期待される結果:

External Secrets Operator configuration with SecretStore reference to AWS Secrets Manager, including refresh interval and secret mapping specification.

セキュリティ監査

低リスク
v1 • 2/25/2026

Static analysis detected 97 patterns but all are false positives. The skill contains documentation (markdown files) with bash command examples for ArgoCD and Flux installation. External command patterns are legitimate kubernetes CLI operations in reference docs, not executable code. Network URLs point to official vendor distributions. Base64 usage is for Kubernetes secret encoding (standard practice), not cryptography.

3
スキャンされたファイル
573
解析された行数
4
検出結果
1
総監査数
低リスクの問題 (2)
External Command Execution in Documentation
Bash commands present in markdown documentation for kubernetes CLI operations. These are instructional examples, not executable code, but users should verify commands before running.
Hardcoded Vendor URLs
Official ArgoCD and Flux distribution URLs are hardcoded for installation. These point to legitimate vendor repositories but should be pinned to specific versions for reproducibility.
監査者: claude

品質スコア

41
アーキテクチャ
100
保守性
87
コンテンツ
50
コミュニティ
86
セキュリティ
91
仕様準拠

作れるもの

Platform Engineer Setting Up GitOps Infrastructure

Establish a complete GitOps pipeline for a new Kubernetes cluster with ArgoCD, including RBAC, SSO integration, and multi-environment deployment strategies.

DevOps Team Automating Application Deployments

Migrate from manual kubectl deployments to automated Git-based workflows with approval gates for production and automated sync for staging environments.

SRE Implementing Progressive Delivery

Configure canary deployments with Argo Rollouts to gradually shift traffic and validate new releases before full production rollout.

これらのプロンプトを試す

Basic ArgoCD Setup
Help me install ArgoCD on my Kubernetes cluster and configure the initial admin access. I need the basic installation manifests and steps to access the UI.
Repository Structure Design
Design a Git repository structure for managing Kubernetes deployments across three environments: development, staging, and production. Include separate directories for applications and infrastructure components.
Sync Policy Configuration
Create ArgoCD Application manifests with sync policies that enable automated sync for staging but require manual approval for production. Include retry policies and sync windows for maintenance periods.
Progressive Delivery Implementation
Configure a canary deployment strategy using Argo Rollouts that shifts 20% traffic initially, pauses for validation, then progressively increases to 100%. Include health checks and automatic rollback conditions.

ベストプラクティス

  • Describe applications declaratively in Git and avoid manual kubectl changes that create configuration drift
  • Store secrets outside Git using External Secrets Operator or Sealed Secrets for sensitive configuration
  • Require manual approval for production syncs while allowing automated sync for non-production environments

回避

  • Commit plaintext secrets or credentials to Git repositories even in private repos
  • Enable automated sync to production without approval gates or sync windows
  • Mix infrastructure and application manifests in the same directory without clear separation

よくある質問

What is the difference between ArgoCD and Flux?
Both implement GitOps but differ in architecture. ArgoCD provides a UI and uses a pull-based model with Application CRDs. Flux is CLI-focused and uses a modular controller approach. Choose ArgoCD for UI-driven workflows or Flux for CLI-centric operations.
How do I handle secrets in GitOps?
Never commit plaintext secrets to Git. Use External Secrets Operator to fetch from AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault. Alternatively, use Sealed Secrets to encrypt secrets before committing.
Can I use GitOps with existing manual deployments?
Yes. Import existing resources into Git by exporting current manifests, then configure ArgoCD or Flux to manage them. Enable self-heal to automatically revert manual changes.
How do I rollback a failed deployment?
Revert the Git commit that introduced the change. The GitOps controller will detect the change and sync the cluster to the previous state automatically. You can also use argocd app rollback or flux suspend commands.
What is the App of Apps pattern?
A pattern where a parent ArgoCD Application manages multiple child Applications. This enables bootstrapping entire environments from a single Application definition and organizing related applications hierarchically.
How do I manage multiple clusters with GitOps?
Use ArgoCD to manage multiple destination clusters by specifying different server URLs in Application manifests. For Flux, bootstrap each cluster separately or use Flux multi-tenancy with cluster selectors.

開発者の詳細

ファイル構成