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.

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

Update helm installer with config for new cpu limiter #8124

Merged
merged 2 commits into from
Feb 9, 2022

Conversation

Furisto
Copy link
Member

@Furisto Furisto commented Feb 9, 2022

Description

#8036 reworked the cpu limiting that ws-daemon is doing. We also need to update the helm installer with the new configuration for ws-daemon. This broke staging as ws-daemon expected the new configuration but the configmap still had the old configuration.

Related Issue(s)

n.a.

How to test

Open preview environment which has been installed with helm and check that ws-daemon is running and workspaces can be opened

Release Notes

NONE

@Furisto Furisto requested a review from a team February 9, 2022 16:34
@github-actions github-actions bot added the team: workspace Issue belongs to the Workspace team label Feb 9, 2022
@@ -26,7 +26,7 @@ type Config struct {
Enabled bool `json:"enabled"`
TotalBandwidth resource.Quantity `json:"totalBandwidth"`
Limit resource.Quantity `json:"limit"`
BurstLimit resource.Quantity `json:"bustLimit"`
BurstLimit resource.Quantity `json:"burstLimit"`
Copy link
Contributor

Choose a reason for hiding this comment

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

@csweichel heh. I suspect due to this typo bursting might not be working quite right in current gen31 deploy. FYI.

Copy link
Member Author

Choose a reason for hiding this comment

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

The installer also has bustLimit, so it should work. Planning on updating that next.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah you are right! Thank you!

Copy link
Contributor

Choose a reason for hiding this comment

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

the installer uses the same structure, hence would have the same (incorrect) behaviour

@roboquat roboquat merged commit 89950b7 into main Feb 9, 2022
@roboquat roboquat deleted the furisto/cpu-config branch February 9, 2022 16:37
@roboquat roboquat added deployed: workspace Workspace team change is running in production deployed Change is completely running in production labels Feb 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: workspace Workspace team change is running in production deployed Change is completely running in production release-note-none size/S team: workspace Issue belongs to the Workspace team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants