fix-e2e-drift

Detect and fix E2E configuration drift from Helm-dev GKG changes.

34|9|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/gitlabhq/orbit-knowledge-graph --skill fix-e2e-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-e2e-drift
Source: https://github.com/gitlabhq/orbit-knowledge-graph/tree/main/.claude/skills/fix-e2e-drift
Command: npx skills add https://github.com/gitlabhq/orbit-knowledge-graph --skill fix-e2e-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically detects and resolves discrepancies between the end-to-end (E2E) testing environment configuration and the underlying Helm-based infrastructure definitions, preventing silent failures due to configuration drift.

Core Features & Use Cases

  • Automated Drift Detection: Identifies when changes in helm-dev/gkg/ (templates, values, secrets) have not been reflected in E2E configuration files.
  • Systematic Fixes: Provides step-by-step guidance and automated scripts to update E2E files (e.g., e2e/helm-values.yaml, config/e2e.yaml, Rust E2E utilities) based on infrastructure changes.
  • Use Case: After deploying a new feature that modifies GKG's Helm chart values, use this Skill to ensure the E2E environment's helm-values.yaml and related configurations are updated accordingly, preventing test failures caused by mismatched settings.

Quick Start

Run the drift detection script to identify and fix configuration mismatches between Helm and E2E files.

Frequently Asked Questions about fix-e2e-drift

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

FAQPage Schema
How do I fix e2e configuration drift after modifying Helm values?

Fix e2e configuration drift by running automated detection scripts to identify mismatches between Helm charts and e2e files, then applying systematic updates to configuration files like e2e/helm-values.yaml to match the new infrastructure definitions.

What is end-to-end configuration drift in Kubernetes Helm deployments?

End-to-end configuration drift occurs when modifications to Helm chart values or templates are not reflected in e2e testing configurations, leading to silent test failures due to mismatched environment settings.

How do I detect stale e2e test files caused by Helm template changes?

Detect stale e2e test files by executing a Bash-based drift detection script that compares the current GKG Helm configurations against e2e configuration files to identify unapplied changes.

Do I need Bash and Git to detect e2e Helm configuration mismatches?

Yes, resolving e2e Helm configuration mismatches requires Git and Bash scripting to run the specific drift detection scripts needed for diagnosing and remediating the unapplied infrastructure changes.

Can I automatically sync e2e config files with GKG Helm chart updates?

You can automatically sync e2e configuration files with GKG Helm chart updates by using scripts that systematically update e2e/helm-values.yaml, config/e2e.yaml, and Rust E2E utilities based on the infrastructure changes.

Why are my e2e tests failing after a Helm deployment?

E2e tests fail after a Helm deployment when changes to GKG Helm chart values create a configuration mismatch, causing the e2e environment to run tests against stale or incorrect settings.