| BioSimulations Dev | BioSimulations Prod |
|---|---|
| Argo CD | Nginx Ingress | Cert Manager |
|---|---|---|
| Prometheus-Grafana |
|---|
This repository contains the configuration for deploying the BioSimulations platform onto a Kubernetes cluster. The repository is organized to support a GitOps workflow and continuous deployment using ArgoCD. The deployment can be monitored and configured at https://deployment.biosimulations.org
Git Ops is an approach to cluster and deployment management that uses a git repository as the single source of truth for the state of the cluster and deployment. The kubernetes cluster contains an continious delivery application (in our case ArgoCD) which monitors the repository and applies any changes. This allows for strict versioning of deployments and easy reverts incase of any issues. Since all changes to the deployment must go through the git repository, there is no need to worry about changes to the cluster that may be lost if the cluster is recreated or changed. You can learn more about this approach here
The repository is structured as follows:
The top level cluster folder contains the declaration of each app that is running on the cluster. This includes BioSimulations itself, but also other cluster-wide infrastructure, such as Nginx and Cert-Manager. The declarations for each app are located in the argocd folder, while the actual resrouces for each are contained in their own respective folders
This contains the template deployment for BioSimulations. The base and overlay approach comes from the kustomize project. The overlays folder contains various instances of BioSimulations deployments, such as the dev and production environments.
The config folder contains Kustomize template for the creation of config maps that can be loaded into the approriate application for each overlay. The kustomization.yaml file in each overlay points to the appropriate config folder to use for that deployment
The secrets for the application are set up identically to the config, but use the Kustomize secret-generator instead of the config-map-generator. The folder itself is a private git submodule which allows the deployment to be public without revealing the secrets.
Contains files and config that are not deployed. This is a staging area for experiments, past approaches, and various resources that are relevant
Make sure you have kubectl installed. If you are connecting to the BioSimulations cluster hosted on Google Cloud you will also need the Google Cloud SDK installed.
This will vary based on your cluster provider. For the main BioSimulations cluster on Google Cloud, first ensure that you are added to the biosimulations organization. Then run the following command:
gcloud container clusters get-credentials biosimulations --zone us-central1-c --project biosimulations
This will automatically configure your kubectl context to the connect to cluster.
The applications are automatically installed and managed using ArgoCD. The following steps will install ArgoCD on your cluster, deploy the cluster-wide infrastructure, and deploy the applications.
kubectl apply -k cluster/
Apply the cluster secrets folder, and create the secrets. These secrets are used to
- authenticate with the this repository, and the secrets submodule repository
- provide the client secret to enable the GitHub SSO
Run the following command:
kubectl apply -n argocd -f secrets/cluster
You should now be able to access the ArgoCD UI at https://deployment.biosimulations.org. When first deployed, it is possible that the SSL configuration is not yet ready. Your browser may prevent you from accessing the UI. If this is the case, determine how to disable HSTS on your browser and try again.
The ArgoCD UI is configured to use GitHub authentication. To login, you will need to provide your GitHub username and password and be a member of the "deployment" team in the biosimulations organization.
It is also possible to login using the admin account in the event that the Github authentication is not yet working. To login as the admin user you will first need to enable the admin account. In the 'cluster/argocd/argo-cm.yaml' file, change the 'admin.enabled' value to 'true'. Then, run the following command to determine the admin password:
kubectl get secrets -n argocd argocd-initial-admin-secret --template={{.data.password}} | base64 --decode
It is highly recommended that you disable the admin account once you have verified that the GitHub authentication is working.
Once the setup is complete, any changes to the configurations will automatically be applied to the cluster by ArgoCD. This can be monitored at https://deployment.biosimulations.org