Trial-backend is a simple TypeScript API used for demonstration purposes. It deploys into a Kubernetes Cluster and communicates with two datastores (PostgreSQL / Redis) to store sample information.
Use the package manager yarn
yarn install
yarn startDependant infrastructure declaration can be found in the following directories:
infra/app-services -> Supporting infrastructure for the trial-backend service (PostgreSQL db, Redis cache) defined with Pulumi. Managed by the trial-backend team.
infra/manifests -> Application deployment files, defined with Kustomize. Managed by the trial-backend team.
Base layer infrastructure (Networking, Kubernetes cluster, etc) is defined in the trial-infra repository. Managed by the platform team.
Changes in the dependant infrastructure (infra/app-services) are managed by the following GitHub Actions:
- infra-preview: Runs with every Pull request to preview the infrastructure changes. The Pulumi bot post back the result of the preview in the PR.
- infra-staging-deploy: Runs with every merge into the main branch, deploy the changes into the infrastructure.
There is an open issue to improve this workflow by implementing the Pulumi Kubernetes operator. This will provide an ArgoCD like experience for infrastructure deployments.
ArgoCD takes care of reconciling the desired state of the service by monitoring the infra/manifests folder.
This workflow has multiple triggers:
-
Every change that requires a new image version triggers the build workflow, which after testing, building and uploading a new image into the ERC repository, it commits a new image tag into the infra/manifests/overlays/staging/kustomization.yaml file, at which point ArgoCD takes care of applying that desired state.
-
Changes in the infra/manifests folder (not associated with a new image tag) are automatically applied into the cluster by ArgoCD.
The ArgoCD self-healing feature prevents configuration drifts done manually, by syncing the live cluster state with the desired configuration.
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Please make sure to update tests as appropriate.