Skip to content

Update the infrastructure section of the handbook - first iteration

https://about.gitlab.com/handbook/engineering/infrastructure/production-architecture/ needs a refresh. @andrewn has done a bit of work in https://gitlab.com/gitlab-com/infrastructure/issues/4675 which would serve as a great starting point to update the diagrams. I think we should probably keep the scaffolding and just do a big update to make it relevant for GCP.

cc @gl-infra @andrewn

  • ## On this page
  • ## Other Related Pages
  • ## Current Architecture - needs an update
  • ## Proposed Cloud Native Architecture - needs an update
  • ### GitLab.com Production Environment - consolidate with current architecture
  • ### High Level Components View - Borrow diagrams from the readiness review?
  • ### Pods Definition - This can probably stay as-is but maybe could use an update?
  • ### Database Architecture - Needs an update
  • ### Monitoring Architecture - Needs an update
  • ### Logging Architecture - Either reference or put link to the logging page
  • ## Infrastructure "Services" and Their SLx's - I think we should remove this until we have a solid plan, cc @Andrew
  • ## Host Naming Standards - Update for gcp
  • ### Hostnames - Update for gcp
  • ### Service Tiers - This is pretty much the same
  • ### Environments - Needs update
  • ### Locations - update for GCP
  • ### TLD Zones needs update for internal and .gitlab.net addresses
  • ### Examples- needs update
  • ## Internal Networking Scheme - replace with pointer to terraform
  • ### Production - remove
  • ### Canary - remove
  • ### Staging - remove
  • ### GitLabGeoPrd - remove
  • ### GitLabGeoStg - remove
  • ### GitLabOps - remove
  • ### Remote Access - Replace with pointer to howtos for bastion access
  • ## Azure - remove
  • ### Load Balancers - Remove, covered in high level diagrams
  • ### Service Nodes - remove
  • ## Digital Ocean - needs update
  • ## AWS - needs update
  • ## Google Cloud - remove as we are on gcp now
  • ## Monitoring - keep, reference to monitoring section
  • ## Technology at GitLab - more or less the same.
Edited by John Jarvis