Prepare and deploy Production environment

[dpordomingo]

In order to have a Production environment we need:

• Retrieve data:
  • to know the HOSTNAME to be used for production,
  • to create and communicate the new GA_TRACKING_ID for testing purposes → Create and communicate the new GA_TRACKING_ID for testing purposes #216
  • create a new GitHub OAuth application for prod, using Prod callback → Create a new GitHub OAuth App for Prod env #217
  • to communicate to @src-d/infrastructure the secrets of the new GitHub OAuth application
• Prepare the environment:
  • .drone.yml and helm charts → Configure the Production environment #218
• Deploy
  • configure Kubernetes secrets → https://github.com/src-d/issues-infrastructure/issues/152
  • stop the annotation process being done in Staging, → [WIP] release/v0.1 Adding UASTs + Going to Prod #237
  • deploy CAT into Staging → unauthorizing all no @src-d/applications members,
  • deploy CAT into Prod
• Create the Production internal DB
  • download, modify and upload the new version of the internal DB into Prod and Staging → Add UAST to old FilePairs #214
• Test and celebrate:
  • configure GA pannels → Configure Google Analytics pannels for Prod and Staging after the migration  #241
  • notify CAT users that from now on it should be used the Production env,

[rporres]

hostname: code-annotation.srcd.run
ingress.globalStaticIpName: code-annotation-production

Helm chart is the same, only the values passed change

(hostname edited by @dpordomingo as agreed by #217 (comment))