Provide K8S Charts for Console Cloud Deployment

[graikhel-intel]

Description of Request

Dependencies

• Implement Secrets Management and Provisioning Flows in Console + RPC-Go to support cloud deployment Implement Secrets Management and Provisioning Flows in Console + RPC-Go to Support Cloud Deployment #597

Scope

• Publish Docker Image - Internal Docker Registry
• Create/Update K8s Charts (compatible with helm)
  • Ideally leverage existing deployment and update with Console (replace MPS and RPS). Should use Postgres, Kong, MPS Router, K8s secrets/Hashicorp Vault, etc...
  • Branch of cloud-deployment repo to be cloud branch
• Review Docs - Identify what needs to be updated
• ACI - out of scope (this is what e2e uses)
• Focus on local k8s only

Acceptance Criteria:

• Test full e2e w/KVM
• Deploys on local k8s cluster

Open Questions / Needs Brainstorming

MPS-Router integration details (out-of-scope)

What’s the integration plan with MPS-Router (which routes API requests to the correct MPS when multiple MPS instances exist)?
Plan to leave alone, update service name to be console-router.

Reuse or new component? Decide whether to: Reuse and extend the existing MPS-Router, or Create a new routing component? Hopefully re-use, document if not able