Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
delivery
delivery
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 357
    • Issues 357
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • GitLab.com
  • GitLab Infrastructure Team
  • deliverydelivery
  • Issues
  • #1382

Closed
Open
Opened Dec 01, 2020 by John Jarvis@jarvOwner

Investigate traffic to the git VMs

Now that websockets / git-ssh / git-https has been migrated to the Kubernetes, and all git VMs are configured as backup servers, we should not see any requests being sent to the git fleet.

this does not appear to be the case currently: https://log.gprd.gitlab.net/goto/2b71d289ca24ba54012588e3560b4c04

We can also see that git gke backends are going down occasionally, which corresponds to the traffic being sent to the git-* fleet.

GKE servers in HAProxy should be available 100% of the time, do these down events correspond to deployments? Something else?

We need to investigate this before removing the git fleet as backup servers.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-com/gl-infra/delivery#1382