promotion-pipeline

Promote OCI artifacts from PR changes through validation to live environments.

24|3|Updated Mar 31, 2022
One-click install
npx skills add https://github.com/ionfury/homelab --skill promotion-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promotion-pipeline
Source: https://github.com/ionfury/homelab/tree/main/.claude/skills/promotion-pipeline
Command: npx skills add https://github.com/ionfury/homelab --skill promotion-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes OCI artifacts from PR changes through validation and deployment to live environments, providing a clear, auditable path for releases and easier rollback when issues arise.

Core Features & Use Cases

  • End-to-end promotion pipeline from PR merge through integration validation to live deployment.
  • Tagging and traceability with RC and stable X.Y.Z tags and commit SHAs for auditability.
  • Observability and rollback support via Flux reconciliations and repository_dispatch events for manual intervention.
  • Use Case: When debugging why a change hasn't reached a cluster or when performing manual promotion to production.

Quick Start

Merge a PR that updates the platform manifest to trigger the promotion pipeline and monitor the GitHub Actions and Flux logs for progress.

Frequently Asked Questions about promotion-pipeline

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

FAQPage Schema
How do I promote OCI artifacts from a PR to production with GitHub Actions?

Promote OCI artifacts by merging a PR that updates the platform manifest, triggering a pipeline that validates, tags with RC and stable X.Y.Z labels, and deploys to live environments via GitHub Actions.

How does Flux reconciliation handle OCI artifact deployment to Kubernetes clusters?

Flux reconciliation continuously monitors the repository for manifest updates, automatically pulling and deploying the promoted OCI artifacts to integration and production clusters to maintain live environment configuration parity.

Why hasn't my OCI artifact reached the live cluster after PR merge?

Debugging OCI artifact promotion involves checking GitHub Actions logs for build or validation failures and reviewing Flux reconciliation logs to confirm the updated manifest successfully deployed to the target cluster.

Can I trigger manual artifact promotion using repository_dispatch events?

Manual promotion to production is supported using repository_dispatch events, which trigger intervention workflows for promoting validated OCI artifacts and providing observability into the deployment lifecycle.

What is the best way to trace OCI artifacts across development and production clusters?

Traceability is maintained by tagging OCI artifacts with release candidate, stable X.Y.Z versions, and commit SHAs, providing an auditable path across the build, validation, and promotion lifecycle stages.

Do I need Flux to manage rollback for promoted OCI artifacts?

Flux supports rollback and observability by reconciling cluster states against the repository, while repository_dispatch events enable manual intervention to revert to previous stable OCI artifact tags when issues arise.