Once the namespace has been created and all of the required secrets added, deployment of OwlDQ can begin.
Installs Web, Agent, and Metastore. OwlDQ is inaccessible until an Ingress or another type of externally accessible service is added manually.
All of the following examples will pull containers directly from the Collibra DQ secured container registry. In most cases, InfoSec policies requires that containers are sourced from a private container repository controlled by the local Cloud Ops team. Make sure to to add
--set global.image.repo=</url/of/private-repo> to make sure that only approved containers are used.
Minimal install, plus preconfigured NodePort or LoadBalancer service to provide access to Web.
LoadBalancer service type will requires that the Kubernetes platform is integrated with a Software Defined Network solution. This will generally be true of major cloud vendor's Kubernetes service. Private cloud platforms more commonly use Ingress controllers. Check with the infrastructure team before attempting to use LoadBalancer service type.
Install with External Service but with SSL enabled.
Make sure that a keystore containing a key is already deployed to the target namespace with a secret name that matches global.web.tls.key.secretName argument (owldq-ssl-secret by default). Also, make sure that the Secret's key name matches the global.web.tls.key.store.name argument (dqkeystore.jks by default).