Skip to content

Deploying from OperatorHub on OpenShift

Scott Trent edited this page Jun 24, 2024 · 6 revisions

Initial steps to deploy OperatorHub bundle of SusQL:

Create the following file called catalogsource.yaml:

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: operatorhubio-catalog
  namespace: openshift-marketplace
spec:
  sourceType: grpc
  image: quay.io/operatorhubio/catalog:latest
  displayName: Community Operators
  publisher: OperatorHub.io
  updateStrategy:
    registryPoll:
      interval: 10m

Apply the changes:

oc apply -f catalogsource.yaml
oc patch -n openshift-marketplace OperatorHub cluster --type merge -p '{"spec":{"sources":[{"name":"operatorhubio-catalog","disabled":false},{"name":"community-operators","disabled":false}]}}'

Next use the OpenShift web console to install the SusQL operator:

  • Click on "Operator->OperatorHub"
  • Search for SusQL
  • Click on it, and follow the GUI prompts to install.

Post Install Customization

After installation, click Operators->Installed Operators->SusQL->YAML, then edit one of the values under spec.install.spec.deployments.labels.spec.template.spec.containers.resources.env.name.values then save the YAML file. The operator will automatically restart with the newly specified value(s).

Currently the following variables can be modified. Searching directly for these variables may be more efficient than perusing the entire YAML.

  • KEPLER-PROMETHEUS-URL
  • KEPLER-METRIC-NAME
  • SUSQL-PROMETHEUS-DATABASE-URL
  • SUSQL-PROMETHEUS-METRICS-URL
  • SAMPLING-RATE
  • LEADER-ELECT
  • HEALTH-PROBE-BIND-ADDRESS
  • METRICS-BIND-ADDRESS
Clone this wiki locally