deployment

Automate deployment workflows and Helm chart management in GitOps-driven Kubernetes/OpenShift environments.

Updated Apr 7, 2026

Search Tags:#deployment #charts #kubernetes #helm #gitops #argocd

Ready to run

npx skills add https://github.com/sayaya1090/handbook --skill deployment-sayaya1090

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/sayaya1090/handbook/tree/main/.gemini/skills/deployment
Command: npx skills add https://github.com/sayaya1090/handbook --skill deployment-sayaya1090

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

배포 프로세스와 Helm 차트 구조의 복잡성을 간소화하고 운영팀이 GitOps를 통해 안정적으로 릴리스를 수행하도록 돕습니다.

Core Features & Use Cases

2계층 GitOps 구조와 Helm 차트 구성을 문서화하고, 운영자 배포를 단순화합니다.
ArgoCD, Gateway, OpenShift와 같은 도구를 활용한 프런트/백엔드 서비스의 배포 파이프라인을 명시합니다.
다수의 스테이지(dev/staging/prod)에서의 일관된 배포 흐름 및 롤백 전략을 제공합니다.

Quick Start

배포/릴리스 작업을 시작하려면 운영 문서에 따른 Helm 차트 배포 절차를 따르세요.

Frequently Asked Questions about deployment

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

FAQPage Schema

How does a 2-layer GitOps deployment model work with Helm charts?▼

A 2-layer GitOps deployment model separates operator-managed Helm chart structures from environment-specific fragments, allowing ArgoCD to automate syncs while maintaining distinct dev, staging, and prod release trains.

How do I manage multi-stage Helm chart promotions in Kubernetes?▼

Multi-stage Helm chart promotions are managed through GitOps-controlled policies that document chart ownership and environment-specific fragments, ensuring controlled and automated syncs across dev, staging, and prod.

Does this deployment approach support OpenShift and ArgoCD together?▼

Yes, the deployment workflow explicitly supports GitOps-driven Kubernetes and OpenShift environments, utilizing ArgoCD applications to manage Helm chart structures and infrastructure deployments.

What is the best way to document chart ownership and promotion policies in GitOps?▼

Documenting chart ownership and promotion policies in GitOps involves defining a 2-layer architecture that maps operators to chart structures and codifies automated sync rules for controlled release trains.

Why use a 2-tier architecture for Helm-based deployment and GitOps?▼

A 2-tier architecture simplifies deployment complexity by separating infrastructure chart management from application releases, enabling operators to streamline Helm-based workflows and rollback strategies reliably.

Can I define rollback strategies for multi-stage release trains in Helm?▼

Yes, the deployment model provides consistent deployment flows and rollback strategies across multiple stages, ensuring stable releases within a GitOps-driven Kubernetes environment.