Make a new deployment outside of GCP, fix resulting issues

[djmitche]

I'm working on this with @MasterWayZ.

Issues encountered:

• update development-process.md (Reorganize docs on dev deployments #4638)
  • move to another file, since this is not required for development
  • azure account is not required
  • postgres version 11.x
• Is Helm 2 still supported? (Minor updates to dev docs #4758)
• AWS is not required initially (after Deprecate s3 artifact support contingent on S3 service configuration #4549 lands)
• CloudAMQP's free tier is not enough (doesn't allow managing users, perms) (Minor updates to dev docs #4758)
• support for non-GKE clusters (Support non-GKE clusters in Helm #3295)
• bugs in dev:init (Fix some minor bugs in yarn dev:init #4757)
• TC requires RabbitMQ use TLS (Make it so that you can specify rabbitmq to use TLS or not #4648)
• yarn build --push tries to push to the official repo (Allow customizing the docker image base name in yarn build #4649)

[djmitche]

@MasterWayZ how's this going? Are there issues to file based on your notes? Maybe even PRs? :)

[MasterWayZ]

I created issue #4739 with PR #4740.

For monopacker I made issue mozilla-platform-ops/monopacker#95 and PR mozilla-platform-ops/monopacker#96

[djmitche]

I think everything here is broken out into other issues or PRs -- @MasterWayZ is there anything else you would like to address here, or should we close this issue?

[MasterWayZ]

@djmitche I think we have everything, unless you also would want a doc on setting up the stateless DNS server? Other than that I can't think of anything else.

[djmitche]

I'm hesitant to document that at all! It's really not a sustainable solution, or one we would be comfortable fixing bugs in.