Install Embedded cluster V2 (early access)

Early access

This installation method is in early access. This feature from Replicated is in beta and have some limitations. Please contact support@gitguardian.com.

Introduction

GitGuardian can be installed with an embedded Kubernetes distribution packaged with it and supports deployment on bare metal, private, or public clouds.

Requirements

Before starting the installation, ensure to review the system and network requirements.

Installation

Embedded cluster V2

Please reach to GitGuardian team at support@gitguardian.com to provide you the license ID.

To start the installation, run these commands on your host. This command will run for around 5 minutes, putting in a screen or a tmux session can prevent an interruption due to a loss of connection. Replace the license with the one given by the GitGuardian team.

LICENSE_ID=your_license
curl -f https://replicated.app/embedded/gitguardian/stable -H "Authorization: $LICENSE_ID" -o gitguardian.tgz
tar -xvzf gitguardian.tgz
sudo ./gitguardian install --license license.yaml

tip

Airgap

To use in airgap mode, use this instead:

LICENSE_ID=your_license
curl -f https://replicated.app/embedded/gitguardian/stable?airgap=true -H "Authorization: $LICENSE_ID" -o gitguardian.tgz
tar -xvzf gitguardian.tgz
sudo ./gitguardian install --license license.yaml --airgap-bundle gitguardian.airgap

You will be prompted to enter the Admin console password. This password is used to manage the GitGuardian application and is different from the GitGuardian dashboard password that you will configure later.

If you are prompted to select from multiple network interfaces, choose the one connected to your private network.

This will install a single node-managed Kubernetes cluster with everything it needs to run the GitGuardian application.

Once the installation is completed, instructions will appear on how to access the Admin Console.

Application

With the embedded Kubernetes cluster now set up, let's move on to installing the GitGuardian application.

1. Access the Admin Console with the link provided and configure TLS. You have the option to upload your TLS certificates or use self-signed ones.

2. Enter the password provided at the end of the cluster installation.

3. You can see cluster status (with one node currently). Then click continue.

4. Configure the application by completing all the required fields:

   • Application Hostname: Enter the Fully Qualified Domain Name (FQDN) for the GitGuardian application.
   • Admin User Fields: These fields are used to create the first GitGuardian user. You'll need to change the password upon the first login.

   

   Additional configuration options include:

   • Scaling: Adjust the number of replicas for each application component. For more details, visit the Scaling page.
   • Prometheus: Activate an exporter for Prometheus.
   • TLS Certificate: This is for the GitGuardian Application. You can either use auto-generated self-signed certificates or upload your own. For self-signed or private CA certificates, disable SSL verification for the GitHub webhook. Learn more on the Configure TLS certificates page.
   • Custom Certificate Authority: Provide a custom CA if necessary.
   • HTTP(s) Proxy: Refer to the proxy section if needed.
   • Databases/Datastores: Choose between using embedded PostgreSQL/Redis or an external one. For more information, see Configure your database.
   • Load balancer considerations: To use the embedded cluster behind a load balancer, please read Configure your instance to work behind a load balancer.

5. Check if preflight checks pass.

Requirements

Preflight checks are critical for a successful installation. The following rules apply:

• ❌ Preflight Check Failures: If preflight checks fail, the installation must not continue until the targeted environment meets all requirements. Please reach out to our support team if needed.
• ⚠️ Preflight Check Warnings: If preflight checks return warnings, the installation can proceed, but it is recommended that you address these warnings to comply with our recommendations.

6. Launch

The first installation of the GitGuardian application requires a few minutes to create all database objects. Once the process is completed, you will be able to log in to the dashboard using the administrator user you defined.

Save the Data Encryption Key

caution

GitGuardian encrypts all sensitive information in the database using an encryption key (aka Django Secret Key). In case of disaster recovery, this key will be needed to restore your data.

You should save it and keep it in a secure location. Use the following command to display the key:

kubectl get secrets gim-secrets -o jsonpath='{.data.DJANGO_SECRET_KEY}' | base64 -d

If needed, specify the Kubernetes namespace with --namespace (default namespace is used if not specified).

Troubleshooting

If you encounter any issues during the installation process, you can generate a support bundle to get proper support from the GitGuardian team: see the support bundle documentation.

Was this page helpful?