About an Edge site installation
After creating your Edge sites in Collibra Data Intelligence Platform, you have to install the Edge software on either the bundled k3s in the Edge site installer or one of the following managed Kubernetes clusters:
- Azure Kubernetes Service (AKS)
- AWS Fargate using EKS
- Amazon EKS (EKS)
- Google Kubernetes Engine (GKE)
- OpenShift
You typically install Edge sites within the same secure environment as the relevant data source. A customer usually has several Edge sites depending on their requirements, for example the number of networks and secure environments, as well as the technical and legal spread of data sources.
Edge sites installed on a managed Kubernetes cluster after the 2024.05 release can be installed in one of the following ways:
- Edge Command Line Interface - our recommended installation method.
- Helm chart - a manual installation method. You need to deploy the Edge helm chart and all prerequisite resources required by Edge, such as configmaps and secrets. You may want to use this method if you are automating the installation process in your own CI/CD environment. Important You should only use the Helm Chart installation method if you are familiar with helm and Kubernetes. As such, Collibra Support is limited and they cannot assist with custom helm and Kubernetes configurations.
An Edge site can have:
- Zero or more predefined connections to data sources via a JDBC driver.
- One or more integration capabilities to process data on site and send the results to Collibra.
An Edge site is a compute run-time on the Kubernetes cluster, that executes capabilities close to your data but that is configurable from the Collibra Data Intelligence Platform settings. It has a dedicated unique identifier and handles data sources that it can reach within its network. You can have more than one Edge site, depending on the number of networks, security domains, regions or VPCs that you have.
Properties
Property | Description |
---|---|
Name |
The name of the Edge site. Use a meaningful name, for example NetherlandsDataCentre1. Do not use spaces or special characters. This field is mandatory and the name must be globally unique. |
Status |
The status of the Edge site. The status is automatically shown when you create an Edge site. |
ID |
The unique ID of the Edge site, which is generated automatically when you create the Edge site. |
Description |
The description of the Edge site. We recommend to put at least basic location information of the Edge site. This field is mandatory. |
Installer and property files |
This section is only visible when the Edge site has the status To be installed. |
Statuses
The status of an Edge site indicates if the Edge site can be used or not. The status is shown on the Edge settings page of the Collibra settings. An Edge site can have one of the following statuses:
Status | Description |
---|---|
To be installed |
The Edge site is created, but not installed yet. |
Offline |
Collibra cannot reach the Edge site. This can be caused by an unsuccessful installation or a lost connection. See the installation logs for more information. |
Unhealthy |
Collibra can connect to the Edge site, but some functions don't work correctly. This is typically caused by problems during the installation. See the installation logs for more information. |
Healthy |
The Edge site installation was successful. |
Installation directories on K3S
The Edge site installer installs files in the following directories on your host server:
- /var/lib/rancher/
- /var/log/
- /etc/
- /usr/local/bin/