Install Hybrid Manager on GCP GKE using Helm

Set the environmental variables for Helm install

1. To prepare for the install, specify the container registry URI:

   → WrapCopy

   export CONTAINER_REGISTRY_URI=<local-registry-URI>

2. Set the edb-bootstrap image version:

   → WrapCopy

   export EDBPGAI_BOOTSTRAP_IMAGE_VERSION="<edb-bootstrap-image-version"

   Make sure to change the value of <edb-bootstrap-image-version> to the image version you're targeting for this install.

3. Set the edb-bootstrap Helm chart version:

   → WrapCopy

   export EDBPGAI_BOOTSTRAP_HELM_CHART_VERSION="<edbpgai-bootstrap-helm-version>"

   Be sure to change the value of <edbpgai-boostrap-helm-version> to the edb-pgai Helm chart version you're targeting for this install.

4. Set your EDB Cloudsmith token:

   → WrapCopy

   export EDB_CLOUDSMITH_TOKEN=<edb-cloudsmith-token>

5. Change edb-cloudsmith-token to your EDB Cloudsmith token.

   Note

   For Hybrid Manager version v1.1.0 and later, use the variables upm-istio.cooke_aeskey and upm-istio.openshift_console_domain_name. Ensure you use the correct variable for you HM version and remove the other parameter in the [Helm upgrade command](Install Hybrid Manager using the Helm chart).

After your environment variables are set, you can prepare for the installation.

Prepare for the installation

1. Add the Helm chart repository from EDB Cloudsmith:

   → WrapCopy

   helm repo add enterprisedb-edbpgai "https://downloads.enterprisedb.com/${EDB_CLOUDSMITH_TOKEN}/pgai-platform/helm/charts/"

2. Update the repository you just added:

   → WrapCopy

   helm repo update

3. Retrieve the default edbpgai-bootstrap Helm values.yaml file:

   → WrapCopy

   helm show values enterprisedb-edbpgai/edbpgai-bootstrap > values.yaml

4. Edit the values.yaml file to the correct values, replacing the environmental variables you set earlier where appropriate:

system: "gke"
containerRegistryURL: "${CONTAINER_REGISTRY_URI}"
bootstrapImageName: "${CONTAINER_REGISTRY_URI}/edbpgai-bootstrap/bootstrap-gke"
bootstrapImageTag: "${EDBPGAI_BOOTSTRAP_IMAGE_VERSION}"
  global:
    default_ingress_domain: "${DEFAULT_INGRESS_DOMAIN}"
    portal_domain_name: "${PORTAL_DOMAIN_NAME}"
  transporter-rw-service:
    domain_name: "${TRANSPORTER_RW_SERVICE_DOMAIN_NAME}"
  transporter-dp-agent:
    rw_service_url: "https://${TRANSPORTER_RW_SERVICE_DOMAIN_NAME}/transporter"
  transporter-data-operator:
    fips_enabled: ${TRANSPORTER_FIPS_ENABLED}
  upm-beacon:
    server_host: "${BEACON_SERVICE_DOMAIN_NAME}"
  upm-istio-gateway: 
    cookie_aeskey: "${AES_256_KEY}"
pgai:
  portal:
    authentication:
      staticPasswords:
        - email: "${AUTHENTICATION_EMAIL}"
          hash: "${AUTHENTICATION_HASH}"
          username: "${AUTHENTICATION_USERNAME}"
          userID: "${AUTHENTICATION_USER_ID}"

Enable dynamic image discovery

To enable the dynamic image discovery from the registry, you need to configure it with the needed options. See Image discovery configuration for detailed instructions on how to do this.

After identifying the required image discovery configuration, update values.yaml with the appropriate settings.

For example, the following is a sample configuration that uses a Google Artifact Registry in the us-east1 region with "basic" authentication:

beaconAgent:
  location: "devspatcher"
  beaconDBConnected: true
  plaintext: true
  logLevel: "debug"
  inCluster: true
  provisioning:
    provider: "gcp"
    imageDiscovery: true
    loadBalancersEnabled: true
    imagesetDiscoveryAuthenticationType: "basic"
    imagesetDiscoveryContainerRegistryURL: "us-east1-docker.pkg.dev"
  providers:
    - appliance
beaconServer:
  logLevel: "debug"

Install Hybrid Manager using the Helm chart

With everything prepared, you can install Hybrid Manager using the edbpgai-bootstrap Helm chart:

helm upgrade \
    -n edbpgai-bootstrap \
    --install \
    -f ./values.yaml \
    --version "${EDBPGAI_BOOTSTRAP_HELM_CHART_VERSION}" \
    edbpgai-bootstrap enterprisedb-edbpgai/edbpgai-bootstrap

You can then monitor the install process using the following command. It takes about 20-30 minutes.

kubectl logs -f -l app=edbpgai-bootstrap -n edbpgai-bootstrap

After the install completes successfully, update DNS zone records and verify the install.