Skip to content

feat: add fault corrupted-kubernetes-secret-credentials (SPAI-414) - #894

Open
Aliciapet11 wants to merge 5 commits into
itbench-hub:mainfrom
Aliciapet11:feat/fault-corrupted-secret-credentials
Open

feat: add fault corrupted-kubernetes-secret-credentials (SPAI-414)#894
Aliciapet11 wants to merge 5 commits into
itbench-hub:mainfrom
Aliciapet11:feat/fault-corrupted-secret-credentials

Conversation

@Aliciapet11

Copy link
Copy Markdown
Contributor

Summary

  • Add new fault type corrupted-kubernetes-secret-credentials and scenario 120 derived from 3 real Konflux Web RCA incidents
  • Fault mechanism: Corrupts Secret data with invalid credentials
  • Includes molecule test for CI validation

New Files

  • Fault definition: scenarios/sre/library/indexes/faults/36.json
  • Injection task: scenarios/sre/project/roles/faults/tasks/inject_corrupted_kubernetes_secret_credentials.yaml
  • Molecule test: scenarios/sre/project/roles/faults/molecule/inject_corrupted_kubernetes_secret_credentials/
  • Scenario index: scenarios/sre/library/indexes/scenarios/120.json

Test plan

  • make validate-library passes
  • Molecule test provided (inject_corrupted_kubernetes_secret_credentials)
  • Live cluster test with OpenTelemetry Demo

🤖 Generated with Claude Code

@Red-GV Red-GV left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So sorry about the delay. I'm just beginning to get a chance to look at these. Got a couple of comments on this one.

Comment thread scenarios/sre/library/indexes/scenarios/63.json
Comment thread scenarios/sre/library/indexes/faults/36.json
Aliciapet11 and others added 2 commits July 12, 2026 18:11
Add new fault type and scenario derived from real Konflux production
incidents (Web RCA data).

- Fault 36: Corrupted Kubernetes Secret Credentials (3 real incidents)
- Scenario 120: Applied to OTel Demo email service
- Includes molecule test for fault injection validation

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Rename scenario 120 → 63 and add scenario template (63.yaml.j2)
- Add fault template (36.yaml.j2)
- Fix YAML indentation in converge.yml
- Add pragma allowlist secret comment in create.yml
- Change verify assertion to != original value (supports random corruption)
- Rewrite injection to read existing secret keys dynamically and corrupt
  with random values instead of hardcoded fields

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Aliciapet11
Aliciapet11 force-pushed the feat/fault-corrupted-secret-credentials branch from 5c9df40 to 09cb1dc Compare July 13, 2026 07:01
@Red-GV Red-GV changed the title feat: add fault [Corrupted Kubernetes Secret Credentials] (SPAI-414) feat: add fault corrupted-kubernetes-secret-credentials (SPAI-414) Jul 16, 2026

@Red-GV Red-GV left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few more things here.

Comment thread scenarios/sre/templates/library/indexes/scenarios/63.yaml.j2 Outdated
Aliciapet11 and others added 3 commits August 2, 2026 12:17
- Change scenario template to use releases[] instead of managers[]
- Remove direct pod deletion from injection task
- Add delete-workload-pods waiter in postInjection targeting email deployment

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add fault ID to argument_specs.yaml choices and task_files.yaml mapping
so the faults role recognizes the new injection task.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Fix molecule.yml indentation to match project conventions
- Wrap long description line in groundtruth_v1.yaml to stay under 160 chars

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Red-GV

Red-GV commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

@Aliciapet11 Can you please sign your commits?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants