MODERATE Cloud Infrastructure

This repository contains the computing infrastructure for the MODERATE Horizon Europe project. It is based on Terraform. Terraform follows the Infrastructure-as-Code (IaC) approach, allowing developers to define cloud resources through code in a reusable and reproducible way.

Credentials

To use both Google Cloud and Terraform Cloud services, you must provide credentials. Specifically, you first need to obtain user access credentials for Application Default Credentials (ADC) using the gcloud CLI.

gcloud auth application-default login

Additionally, you must log in to Terraform Cloud using the Terraform CLI:

terraform login

Usage

To deploy the infrastructure, you may run the following command:

task apply-prod

This will do the following:

• Initialize the Terraform workspace.
• Apply the Terraform configuration to the cloud provider.
• Fetch the credentials for the Kubernetes cluster and configure the local kubectl client.
• Update the DNS records to point to the Kubernetes cluster.

About the MODERATE CLI image

The MODERATE CLI is a utility to interact programmatically with the MODERATE infrastructure. Its main objective is to contain the logic necessary to automatically initialize some services that require configuration that cannot be achieved through Terraform alone. For example, the MODERATE CLI is used to create the initial realm in Keycloak.

The image needs to be built locally and pushed to a public registry for the Kubernetes Jobs that are defined in the Terraform configuration to be able to pull it. To build and push the image, run the following command:

task push-cli-image

By default the image is published in Docker Hub under the agmangas/moderate-cli repository. However, this can be configured in the Taskfile.yml file.

Manual steps

Updating the DNS records

The DNS records for the moderate.cloud domain are managed by Google's Cloud DNS. It is necessary to manually update these records to point to the newly created NGINX Ingress load balancer. This is achieved by running the update-dns.sh script.

Please note that when using the task apply-prod task this will be automatically done for you.

Configuring the OpenMetadata JWT token

The Dagster assets that run the metadata workflows require a JWT token to authenticate with the OpenMetadata service. However, this token can only be generated manually in the OpenMetadata web UI. To do so, access the Settings > Integrations > Bots section and revoke the existing token to generate a new one.

Then, add the new token to the open_metadata_token variable in the variables.auto.tfvars file of the gcp_prod Terraform module. Re-apply the Terraform configuration to update the Kubernetes secrets.

Edit authentication flows in Keycloak

Some of the applications depend on Keycloak to restrict access to users with a specific role. This is not done automatically, due to this particular interaction not being supported in the utility package that is used to manage Keycloak. Therefore, it is necessary to edit the authentication flows in Keycloak to include a condition that checks for the appropriate role.