Add Staging deployment to sidestream cluster

[DeusAvalon]

Adds the workflow to deploy into the sidestream kubernetes cluster via ArgoCD.

Workflow got fully tested here

Deployment Value Files can be found in the sidestream-tech/k8s-projects repo

New URL is:
https://powerhouse.switchboard.k8s.sidestream.tech

[DeusAvalon]

@valiafetisov @BracketJohn I would have loved to use our @powerhouse-inc/Sidestream team but because the GitHub Team is a set to secret it cannot be used in a CO file.

See the other CO file in the k8s-projects repo:
https://github.com/sidestream-tech/k8s-projects/blob/main/CODEOWNERS

And i removed the SyncPolicy for the deployment to prevent auto deployments:
https://github.com/sidestream-tech/k8s-projects/commit/e3f60a612df830732fd480187480fe362aecbad1

[valiafetisov]

Thanks, I think it's enough for this PR

[valiafetisov]

Question: the other open PR #55 introduces new API_ORIGIN env variable for the api service that have to be set in staging/production (to the url at which the service is running, e.g. https://powerhouse.switchboard.k8s.sidestream.tech).
Do I need to now open another PR to the sidestream-tech/k8s-projects repo in order to set it before merging #55?

[DeusAvalon]

Yes exactly! :) Yes as we also disabled AutoSync for this Application we can just merge both PR's and then manual sync the application in Argo to deploy all the changes at once!

[valiafetisov]

Then, please review https://github.com/sidestream-tech/k8s-projects/pull/2

[valiafetisov]

Also, since you have admin rights in this repo, can you please

• Add requirement (that seems to be lost when the repo was moved) to have at least one approval before merging
  • This might require giving write rights to @KirillDogadin-std and @LukSteib github users
• Protect main branch (if it's not yet done)