upgrading-chart

4
0
Source

Upgrades Helm chart dependencies (PostgreSQL, Vault) in the Chainloop project, including vendorized charts, container images, and CI/CD workflows. Use when the user mentions upgrading Helm charts, Bitnami dependencies, PostgreSQL chart, or Vault chart. CRITICAL - Major version upgrades are FORBIDDEN and must be escalated.

Install

mkdir -p .claude/skills/upgrading-chart && curl -L -o skill.zip "https://mcp.directory/api/skills/download/2467" && unzip -o skill.zip -d .claude/skills/upgrading-chart && rm skill.zip

Installs to .claude/skills/upgrading-chart

About this skill

Upgrading Helm Chart Dependencies

This skill automates the upgrade process for Helm chart dependencies in the Chainloop project. Supports PostgreSQL and Vault (both Bitnami charts).

CRITICAL RESTRICTIONS

Version Upgrade Rules:

  • Patch upgrades (1.2.3 → 1.2.4): ALLOWED
  • Minor upgrades (1.2.x → 1.3.x): ALLOWED
  • Major upgrades (1.x.x → 2.x.x): FORBIDDEN - STOP IMMEDIATELY

MANDATORY: If major version upgrade is detected, STOP the process and inform the user that manual review is required.

Upgrade Types

The skill supports two upgrade types:

  1. Specific Image Upgrade: Update container image to specific version (chart unchanged)
  2. Chart Minor Version Upgrade: Update chart to latest minor version (may include image updates)

IMPORTANT: Container images are ONLY updated as part of chart upgrades, never independently (unless Type 1).

Process

1. Identify Upgrade Type

Ask the user which type of upgrade they want:

  • Type 1: Specific image version upgrade
  • Type 2: Latest minor chart version upgrade

Also ask which chart: postgresql or vault

2. Pre-Upgrade Validation

Check current state:

cat deployment/chainloop/charts/<chart-name>/Chart.yaml | grep "^version:"
cat deployment/chainloop/charts/<chart-name>/Chart.yaml | grep "^appVersion:"

3. Version Compatibility Check

For any version change, validate that major version remains the same:

CURRENT_MAJOR=$(echo "$CURRENT_VERSION" | cut -d. -f1)
TARGET_MAJOR=$(echo "$TARGET_VERSION" | cut -d. -f1)

if [ "$CURRENT_MAJOR" != "$TARGET_MAJOR" ]; then
    echo "FORBIDDEN: Major version upgrade detected"
    exit 1
fi

If major version upgrade detected, STOP and escalate.

Type 1: Specific Image Upgrade

See image-upgrade-process.md for detailed steps.

Summary:

  1. Locate target container image in Bitnami Containers
  2. Find commit with release message pattern
  3. Extract APP_VERSION from Dockerfile
  4. Update deployment/charts/<chart-name>/Chart.yaml appVersion
  5. Update .github/workflows/build_external_container_images.yaml commit hash

Type 2: Chart Minor Version Upgrade

See chart-upgrade-process.md for detailed steps.

Summary:

  1. Locate target chart version in Bitnami Charts CHANGELOG.md
  2. Validate minor version upgrade only
  3. Download and extract target chart
  4. Check for image changes (compare Chart.yaml)
  5. If images changed, update container image references
  6. Vendorize chart update (copy files)
  7. Update dependencies in correct order
  8. Update main chart dependency version
  9. Clean up temporary files

Verification

After any upgrade type, run:

# Lint charts
helm lint deployment/charts/<chart-name>
helm lint deployment/chainloop

# Template validation
helm template deployment/charts/<chart-name>
helm template deployment/chainloop

# Local testing
cd devel && docker compose up

# Verify image consistency
grep -r "appVersion\|image.*tag" deployment/charts/<chart-name>/

Files Modified

See files-modified.md for complete list.

Troubleshooting

Common issues:

  • Image Version Mismatch: Verify APP_VERSION matches Chart.yaml appVersion
  • Build Failures: Check commit reference in build workflow
  • Dependency Conflicts: Verify dependencies updated in correct order (vendorized first, then main chart)

Rollback

If issues occur:

git checkout HEAD -- deployment/
find deployment/ -name "Chart.lock" -delete
cd deployment/chainloop && helm dependency build
cd ../../devel && docker compose down && docker compose up

Important Notes

  • Dex is self-managed and follows a separate process (not covered by this skill)
  • Always use commit hashes for reproducibility
  • Dependencies must be updated in correct order: vendorized chart first, then main chart
  • Container images are found in Bitnami Containers repo, charts in Bitnami Charts repo

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318399

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

340397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

452339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.