Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat(scaletest/templates): add support for concurrent scenarios#11753

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.

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

Already on GitHub?Sign in to your account

Conversation

mafredri
Copy link
Member

@mafredrimafredri commentedJan 22, 2024
edited
Loading

Fixes#10794

This PR includes some other fixes as well.

@johnstcn
Copy link
Member

johnstcn commentedJan 22, 2024
edited
Loading

It might be also good to suspend theHelmRelease manifests so that Flux doesn't trigger a deployment during scale testing.

You can do this by settingspec.suspend: true in the manifest YAML (or JSON, as you wish), and setting them back tofalse afterwards.

$ kubectl get helmrelease -n coder-big big -o yamlapiVersion: helm.toolkit.fluxcd.io/v2beta2kind: HelmReleasemetadata:  [...]  name: big  namespace: coder-bigspec:  [...]  suspend: true  [...]status:  [...]

Alternatively, you can just use theflux CLI and runflux (suspend|resume) helmrelease <release_name>

mafredri reacted with thumbs up emoji

@mafredrimafredri marked this pull request as ready for reviewJanuary 29, 2024 17:14
Copy link
Member

@mtojekmtojek left a comment

Choose a reason for hiding this comment

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

It was a bit hard for me to go through this review due to Bash syntax, so please assume this to be a high-level review 👍

mafredri reacted with thumbs up emoji
# we're creating a lot of workspaces at once and some of them may fail
# due to network issues or other transient errors.
coder exp scaletest create-workspaces \
--retry 5 \
Copy link
Member

Choose a reason for hiding this comment

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

I'm curious if this must be ignored&retried, maybe we should identify and fix problems in a different way, even provisioning workspaces slower?

Anyway, consider it to be a side thought.

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

We would have to ensure terraform registry is cached locally, once we know workspace builds don't use any external networking, we could potentially disable the retry, if we want. 👍🏻

@mafredrimafredri merged commit83eea2d intomainJan 30, 2024
@mafredrimafredri deleted the mafredri/feat-scaletest-add-load-concurrency-and-percentages branchJanuary 30, 2024 12:54
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsJan 30, 2024
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@mtojekmtojekmtojek approved these changes

@johnstcnjohnstcnjohnstcn approved these changes

Assignees

@mafredrimafredri

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Allow the workload for the coder scaletest command to be split up
3 participants
@mafredri@johnstcn@mtojek

[8]ページ先頭

©2009-2025 Movatter.jp