sync-env

Synchronize Kubernetes environment configurations from CI to Staging with Kustomize.

5|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/oldwinter/skills --skill sync-env-oldwinter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-env
Source: https://github.com/oldwinter/skills/tree/main/devops-skills/sync-env
Command: npx skills add https://github.com/oldwinter/skills --skill sync-env-oldwinter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the synchronization of Kubernetes environment configurations between CI, Staging, and Production, ensuring consistency while incorporating safety gates and environment-specific whitelists to prevent accidental misconfigurations.

Core Features & Use Cases

  • Environment Configuration Sync: Propagates Kubernetes configurations (Kustomizations) from a CI environment to Staging, with an optional promotion to Production.
  • Safety Gates & Whitelisting: Implements a strict deployment strategy for Production (manual sync) and maintains a whitelist of configuration items that are expected to differ across environments, preventing unintended changes to critical parameters like database connections, secrets, and Stripe keys.
  • Image Synchronization: Manages the promotion of container image tags across environments.
  • Use Case: After deploying a new feature to CI, use this Skill to automatically sync its configuration to Staging for testing. Once validated, you can selectively promote specific configurations or images to Production following a defined manual approval process.

Quick Start

Use the sync-env skill to compare the configuration differences between CI and staging environments.

Frequently Asked Questions about sync-env

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

FAQPage Schema
How do I sync Kubernetes configurations across CI, Staging, and Production environments?

Sync Kubernetes configurations by propagating Kustomize setups from CI to Staging with automated safety gates, then selectively promoting to Production through a mandated manual approval process to ensure deployment safety.

How does the Kustomize whitelist prevent configuration drift between environments?

The Kustomize whitelist prevents configuration drift by explicitly defining expected environment-specific differences like database connections and secrets, ensuring critical parameters remain unchanged during automated environment configuration synchronization.

How to promote container image tags across Kubernetes deployment stages?

Promote container image tags across deployment stages by synchronizing environment configurations from CI to Staging first, then selectively promoting validated images to Production following the defined manual sync strategy.

Can I use Argo CD with this manual production sync strategy?

Yes, the strict deployment strategy mandates manual intervention for Production synchronization, which aligns with Argo CD workflows by incorporating safety gates before applying Kustomize configurations to critical environments.

What are the limitations of automated Kubernetes environment sync for Production?

Automated Kubernetes environment sync is limited by a strict manual intervention requirement for Production, meaning configurations cannot be automatically promoted without passing safety gates and explicit manual approval.