cloud-bulldozer / cloud-bulldozer/scale-ci-deploy
Scale-ci-deploy defaults should match the installer defaults
- Dominant language
- Jinja
- Stars
- 16
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
The current scale-ci-deploy defaults for various cloud platforms are not the same when compared to the installer. This will cause problems in terms of performance/scale if they are not modified during the scale test runs. We need to check and make sure the defaults like instance type, disk size, disk type e.t.c. match with the installer for all the supported cloud platforms:
- [ ] gcp
- [ ] aws
- [ ] azure
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the scale-ci-deploy defaults and the corresponding installer defaults for each supported cloud platform. Compare instance type, disk size, disk type, and other listed settings for GCP, AWS, and Azure. Done means all three checklist items match the installer defaults and scale test runs use the intended values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, azure, gcp, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100