Enable Profiling for gitlab-sshd
A recent attempt at enabling GitLab-SSHD in production did not go so well. Specifically a larger amount of memory was being utilized and nothing during testing in staging pointed towards memory exhaustion problems. GitLab-Shell uses version 1.7.0 of labkit which includes profiling capabilities. Utilize this issue to setup and configure profiling where gitlab-sshd
is enabled. This includes:
- Staging - main and canary stages
- Preprod
- Production - ONLY the canary stage
I'm opting to NOT enable profiling everywhere because of the fudemental change to the way gitlab-shell works. I don't want to pollute Profiling data which will not apply unless gitlab-sshd
is enabled.
Milestones
-
Terraform changes for workflow identity are made -
Annotations added to the service account where gitlab-sshd
is enabled -
Fix terraform configuration for canary -
Fix GKE terraform module - https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/15189#note_842331524 -
Upgrade GKE module in all environments -
Validate fix works in production
-
-
Cleanup - https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/15189#note_843562823
Edited by John Skarbek