Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[stress testing] Prefix init container names with "init-" #1903

Closed
benbp opened this issue Aug 13, 2021 · 0 comments · Fixed by #2106
Closed

[stress testing] Prefix init container names with "init-" #1903

benbp opened this issue Aug 13, 2021 · 0 comments · Fixed by #2106
Assignees
@benbp
Labels
Central-EngSys This issue is owned by the Engineering System team. pillar-reliability The issue is related to reliability, one of our core engineering pillars. (includes stress testing) Stress This issue is related to stress testing, part of our reliability pillar.

Comments

@benbp
Copy link
Member

benbp commented Aug 13, 2021

The stress test dashboard queries are being built out and it is cumbersome to exclude init containers from certain queries (like container logs and chaos events). Rather than keeping a hardcoded list of known init containers, we should have a convention of every init container having a name prefix of "init-". We could do this with other metadata but it makes the queries more complicated so I think name is best.

  • Update the init container names: azure-deployer and test-env-initializer to "init-azure-deployer" and "init-test-env"
  • Update the stress test workbook queries that exclude these init containers to use <container name field> startswith "init" instead.
@benbp benbp added pillar-compatibility This issue is related to compatibility between versions, one of our core engineering pillars. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Aug 13, 2021
@kurtzeborn kurtzeborn added pillar-reliability The issue is related to reliability, one of our core engineering pillars. (includes stress testing) Stress This issue is related to stress testing, part of our reliability pillar. and removed pillar-compatibility This issue is related to compatibility between versions, one of our core engineering pillars. labels Aug 17, 2021
@kurtzeborn kurtzeborn removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 17, 2021
@benbp benbp added the Central-EngSys This issue is owned by the Engineering System team. label Aug 17, 2021
@benbp benbp mentioned this issue Oct 14, 2021
Merged
@benbp benbp assigned benbp and unassigned ckairen Oct 14, 2021
@ghost ghost closed this as completed in #2106 Oct 22, 2021
ghost pushed a commit that referenced this issue Oct 22, 2021
@benbp
Fully automate stress cluster buildout and add support for azure file…
dd1c8ca 
… share mounting (#2106)

- Fully automate cluster buildout. Add azure file share mount to stress tests.
    - Moving the test/ad-hoc cluster back to the playground subscription
    - Upgrading kubernetes cluster version to 1.21.x to pull in support for the azure csi file driver
    - Adding high memory agent nodes to the base deployment
    - Enabling node autoscaler in the base deployment
- Publish stress watcher image in CI. Run docker build on PR
    - Using common image location across stress clusters to simplify buildout+deployment
- Add stress test debug file share usage example

Resolves #1903
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benbp benbp

Labels
Central-EngSys This issue is owned by the Engineering System team. pillar-reliability The issue is related to reliability, one of our core engineering pillars. (includes stress testing) Stress This issue is related to stress testing, part of our reliability pillar.
Projects
None yet
Milestone
No milestone
3 participants
@benbp @kurtzeborn @ckairen