API Kubernetes migration final readiness review from Development

Welcome to the Infrastructure Readiness Review for the API Service migration into Kubernetes.

Utilize the following handbook page for guidance on how to perform the necessary review: https://about.gitlab.com/handbook/engineering/infrastructure/production/readiness/#reviewing-a-proposal

Upon completion of review, please Approve and unassign yourself from this MR.

Please review the following document and leave your questions inline.

If you have no remarks about the content of the text, consider the following questions:

• Is there enough documentation in our runbooks such that we can recover from a failure of the API?
• Are there appropriate Pages in place such that we get alerted when the API begins to fail?
• Is the documentation in our runbooks sufficient that if the bus factor is high, another member of Infrastructure can successfully configure the API service?
• Is there anything questionable with the method chosen to deploy the API?
• Are there any improvements someone would suggest to either our deployment mechanism, the use of GKE, or the configuration of the API?
• Do team members have knowledge of being able to successfully setup and connect to the Kubernetes Clusters and perform troubleshooting processes?
• Can team members find the logs and dashboards we've created to assist with monitoring both Kubernetes and the API Service?

Infrastructure Team Review: !70 (merged)

Security Team Review: !71 (closed)

Development Review: !72 (closed)

Addresses: delivery#1463 (closed)

Epic: &271 (closed)