Cloud Deployment Tooling

[p5150j]

As a DevOps engineer,
I want to choose Infrastructure as Code (IaaC) tools like Helm for deploying the Gateway stack,
so that I can automate the deployment process and manage the infrastructure efficiently across different cloud environments.

Acceptance Criteria:

• The deployment tooling should be set up initially for AWS.
• The tooling should remain cloud-agnostic to support other cloud providers (e.g., Azure, Google Cloud) in the future.
• Helm charts should be created or updated to deploy the full Gateway stack.
• README Documentation should be provided for deploying the Gateway stack on AWS

Note:
Development teams need to add and relate all necessary implementation subtasks (e.g., creating Helm charts, configuring AWS settings, ensuring cloud-agnostic capabilities) to this story for proper tracking and management.

sub tasks:

• #506
• #507
• #508
• #537
• #538
• #539
• #540

[saraswatpuneet]

Here are some bottom up tasks in my mind for the helm route, starting from a default chart templates

• Define config maps: given many env variables exists, lets find out which ones will go to a config map and which ones are coming from secrets.
• Define secrets mapping (I believe k8s support that now as separate resource) alternatively
• Define Deployment specs and mount any volume/configmaps/secrets
• Define service spec

This should get us going, more complicated parts can be added once base version running a swarm of services gets up and going.

Ideally use service accounts to authenticate the service to access various internal apis since all major cloud providers have service account support