Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat: add fault aggressive-scaledown-kubernetes-horizontal-pod-autoscaler#955

Draft
hugoev wants to merge 2 commits into
itbench-hub:mainfrom
hugoev:feat/aggressive-scaledown-hpa-fault-136
Draft

feat: add fault aggressive-scaledown-kubernetes-horizontal-pod-autoscaler#955
hugoev wants to merge 2 commits into
itbench-hub:mainfrom
hugoev:feat/aggressive-scaledown-hpa-fault-136

Conversation

@hugoev

@hugoev hugoev commented Jul 2, 2026

Copy link
Copy Markdown

Closes #136

Summary

Adds a new fault that configures a Kubernetes HPA to aggressively scale
down workloads — keeping replicas at minimum even under high demand.
This is the SRE/inverse counterpart to the existing
misconfigured-kubernetes-horizontal-pod-autoscaler fault (11) which
only modelled the scale-up (FinOps) case.

Changes

  • New fault: aggressive-scaledown-kubernetes-horizontal-pod-autoscaler
    • Injection task (Ansible)
    • Fault index (index 31)
    • Molecule test (all 5 stages passing)
  • New scenario 115: SRE — frontend HPA aggressive scale-down under load
    • Combines HPA fault + loadGeneratorFloodHomepage feature flag
    • groundtruth.yaml + groundtruth_v1.yaml
  • Schema and documentation updates
  • Added Hugo Villarreal to CONTRIBUTORS.md

@hugoev hugoev force-pushed the feat/aggressive-scaledown-hpa-fault-136 branch 2 times, most recently from 7961bce to 0bc9ace Compare July 2, 2026 18:05
@hugoev hugoev force-pushed the feat/aggressive-scaledown-hpa-fault-136 branch from 0bc9ace to 758d2a4 Compare July 2, 2026 18:09
… 115

- Update fault 31 JSON schema to accept autoscaling/v2 HorizontalPodAutoscaler
- Update scenario 115 to pass HPA directly instead of Deployment
- Regenerate aggressive-scaledown HPA fault JSON schema

Signed-off-by: Hugo Villarreal <[email protected]>
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.

Expansion on Misconfigured HPA Fault

1 participant