elastic/cloud-on-k8s

Improve chaos job

Open

#3,781 opened on Sep 24, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (788 forks)auto 404
:ci>testgood first issue

Repository metrics

Stars
 (2,841 stars)
PR merge metrics
 (PR metrics pending)

Description

The chaos job introduced in #3706 could be improved to make the process less "predictable":

Contributor guide

Research direction
Inspect the existing chaos job code from PR #3706, understand the current replica scaling and delay logic, then explore adding random delays (e.g., with jitterbug) and an immediate scale up step.
Tech stack
gokubernetes
Domain
devopsinfrastructuretesting
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75