deco-site-deployment

Update Kubernetes state secrets and trigger redeploys for Deco sites on AWS and GCP.

5|2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/decocms/deco-start --skill deco-site-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deco-site-deployment
Source: https://github.com/decocms/deco-start/tree/main/.cursor/skills/deco-site-deployment
Command: npx skills add https://github.com/decocms/deco-start --skill deco-site-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deco site configuration is stored in Kubernetes secrets and must be coordinated across multi-cloud deployments. This skill provides a structured workflow to update environment variables, autoscaling rules, and resource limits, then redeploy Deco sites across AWS and GCP clusters.

Core Features & Use Cases

  • Centralized SiteState management via the Kubernetes secret
  • Cross-cloud redeploys ensuring consistent states on AWS and GCP
  • Safe operational steps: read, modify, and patch the state, then trigger redeploys

Quick Start

Coordinate Deco site configs across multi-clouds.

Frequently Asked Questions about deco-site-deployment

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

FAQPage Schema
How do I update Kubernetes secrets to redeploy a site across AWS and GCP?

To redeploy across AWS and GCP, you update the Kubernetes state secret governing your site's environment, scaling, and resources, then push changes and trigger redeploys so both clouds pick up the new configuration.

What is a Kubernetes state secret used for in multi-cloud site deployments?

A Kubernetes state secret stores the centralized SiteState configuration, governing environment variables, autoscaling rules, and resource limits for Deco sites deployed across multi-cloud clusters.

Do I need kubectl and admin API keys to manage Deco site configurations?

Yes, managing Deco site configurations requires kubectl access to clusters, admin API keys, and proper cluster context to ensure safe, coordinated deployments across AWS and GCP environments.

How do I modify autoscaling rules and resource limits for multi-cloud deployments?

You modify autoscaling rules and resource limits by reading, patching, and updating the Kubernetes state secret, then triggering cross-cloud redeploys to ensure consistent states on AWS and GCP.

What are the limitations of coordinating site configs via Kubernetes secrets?

Limitations include requiring proper cluster context and direct kubectl access to safely coordinate deployments; without admin API keys and correct cluster context, safe cross-cloud configuration updates cannot proceed.