runtime-config-flagd

List, inspect, and toggle flagd feature flags in the OTel Demo Kubernetes environment.

656|82|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/incidentfox/incidentfox --skill runtime-config-flagd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-config-flagd
Source: https://github.com/incidentfox/incidentfox/tree/main/sre-agent/.claude/skills/runtime-config-flagd
Command: npx skills add https://github.com/incidentfox/incidentfox --skill runtime-config-flagd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Incident scenarios in the OpenTelemetry Demo are controlled by feature flags stored in a Kubernetes ConfigMap, and manually editing that ConfigMap to inject or remediate failures is error-prone and slow. This Skill provides scripts to list, inspect, and toggle those flags safely through flagd's hot-reload mechanism.

Core Features & Use Cases

  • Scenario Discovery: List all incident scenarios (payment failures, CPU spikes, memory leaks, Kafka lag, LLM errors) with current status, affected service, detection PromQL, and remediation steps.
  • Flag Inspection: View any flag's current variant, value, and all available variants, with JSON output options.
  • Safe Remediation: Toggle flags with a mandatory dry-run workflow before applying changes via ConfigMap patch, triggering flagd hot-reload within seconds.
  • Use Case: During a payment failure incident, run list_scenarios.py --active-only to confirm the paymentFailure flag is active, dry-run set_flag.py paymentFailure off, then apply it to restore normal behavior.

Quick Start

Ask the agent to list the currently active incident scenarios and then disable the paymentFailure flag after a dry run.

Frequently Asked Questions about runtime-config-flagd

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

FAQPage Schema
How do I toggle feature flags in the OpenTelemetry Demo?

Use the set_flag.py script with the flag key and variant, such as set_flag.py paymentFailure off. Always run with --dry-run first to preview the change, then apply it; flagd hot-reloads the ConfigMap within seconds.

How do I list active incident scenarios in the OTel Demo?

Run list_scenarios.py --active-only to show only currently active incident scenarios. The output includes the flag name, current variant, affected service, effect, and remediation steps for each active scenario.

What incident scenarios can flagd flags inject in the OTel Demo?

Flags control payment failures, payment unreachability, ad service CPU spikes and GC pressure, email memory leaks, image latency, Kafka queue problems, cache failures, cart failures, traffic floods, and LLM inaccuracy or rate limit errors.

Does set_flag.py require kubectl access to Kubernetes?

Yes, the scripts call kubectl to read and patch the flagd-config ConfigMap in the otel-demo namespace. When running in-cluster, they use the mounted service account token via a temporary kubeconfig instead of exposing it on the command line.

Why does the email memory leak persist after disabling the flag?

Setting emailMemoryLeak to off stops further leaking, but already-leaked memory is not reclaimed. You must also restart the email pod to fully remediate the OOM condition.