neb-addons-upgrade

Automate end-to-end NebInfra platform addon upgrades across Phases 1-8.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-addons-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neb-addons-upgrade
Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-addons-upgrade
Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-addons-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrade platform addon charts (external-secrets, cert-manager, crossplane, kyverno, monitoring, argo-cd, istio, etc.) from one upstream version to another. Covers the full lifecycle: release note research, cluster CR audit, chart changes, validation, release chain, and live cluster verification. Use when upgrading any addon's upstream dependency version, when asked to "upgrade X to version Y", "bump X", or when investigating what changed between addon versions. Also use when the user mentions "addon upgrade", "operator upgrade", "chart dependency bump", or wants to update any helm-modules-apps chart that wraps an upstream project.

Core Features & Use Cases

  • Phase-driven upgrade workflow spanning research, CR audits, chart changes, validation, release chain, and live verification.
  • Comprehensive risk assessment including upstream version existence checks and deprecation tracking.
  • End-to-end governance and release coordination across wrapper charts and platform components.

Quick Start

Initiate an addon upgrade by specifying the addon and target version and execute Phases 1–8 in order.

Frequently Asked Questions about neb-addons-upgrade

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

FAQPage Schema
How do I automate a Helm chart upgrade for platform addons like cert-manager or argo-cd?

Automate Helm chart upgrades for platform addons by executing a phased workflow spanning research, CR audits, chart changes, validation, release chain coordination, and live cluster verification.

What is included in the end-to-end addon upgrade lifecycle?

The end-to-end addon upgrade lifecycle includes upstream release note research, cluster CR audits, chart dependency bumps, validation across CLIs and clusters, and live cluster verification.

How do I validate an addon upgrade across clusters after a chart dependency bump?

Validate an addon upgrade across clusters by enforcing strong validation phases that include appset version updates, CLI checks, and live cluster verification.

Can I use this workflow to investigate what changed between upstream addon versions?

Yes, you can investigate changes between upstream addon versions by initiating the research phase, which performs upstream version existence checks and deprecation tracking.

Does the addon upgrade automation handle wrapper charts for upstream projects?

Yes, the automation handles helm-modules-apps wrapper charts by applying governance and release coordination across wrapper charts and platform components.