GitLab Dedicated Prospects

The purpose of this page is to hopefully help an SA onboards when they onboard a new Dedicated Customer, what are the considerations and preparation material during the onboarding/discovery phase. Based on past interactions with existing GitLab Dedicated customers and due to the usually longer nature of onboarding customers, a collaboration project is recommended to keep all stakeholders aware and engaged.

A collaboration template specifically for dedicated customers is available as a template here (https://gitlab.com/gitlab-com/account-management/templates/dedicated-collaboration-project).

Most of the details discussed below are also available as individual issues which provides a good place to include your product managers and customers to collaborate.

Dedicated Reference Links

• GitLab Dedicated Issue Tracker Board
• Customer Onboarding Process
• Slack Channel: #f_gitlab_dedicated
• Category Direction Page

Administration

• Who will be the administrator to send the GitLab login credentials to?
• What is your preferred time frame for your maintenance window? (4 hour block)
• For emergency security patches and scheduled upgrades, what email address(es) should the notification be sent to?

User Authentication

• Authentication via SAML
• Authentication via LDAP - Please check with dedicated team (Still part of the roadmap)

Connectivity

• To provide VPC Endpoint details

  • IAM Principal for the AWS user or role in their own AWS Organization that will be establishing the VPC endpoint within the Customer account. GitLab Dedicated will use this IAM Principal for access-control: this IAM principal will be the only one able to setup an endpoint to the service.

• List of AZs (up to 2): Which AZs do you want the VPC endpoint to be available in?

• Reverse PrivateLink: What services are required for private link connectivity (E.g. between JIRA, Confluence, Nexus, Artifactory and GitLab)

URL	Service Name	Port
xxx.com	com.amazonaws.vpce.xx-xxx	443

Disaster Recovery/Geo

• Which region would you like your Geo node to be located?
• Do you have specific requirements for which AZ that you want your setup to be located? (Eg. southeast-1a)

Runners

• Where are your runners located?

• Runner Flavors

  • Openshift

• Strategies on how to connect to GitLab Dedicated

  • Multi-Cloud
    • Leverage on AWS Transit Gateway
      • Example Architecture

Domain - Customer Desired Sub-Domains

• E.g.: <CUSTOMER_NAME>.gitlab-dedicated.com

Desired Instance Storage & Sizing

• This is inclusive of registry as well as all other resources tied to the application (git, etc)

Logging and Security Requirements

• Are you looking for log streaming to an S3 bucket?
• Log Sources to be streamed to S3 bucket and where?
  • production_json.log
  • Production.log
  • api_json.log
  • Application.log
  • Application_json.log
  • audit_json.log