Investigate how to support this feature on Kogito Operator
You can view the staged docs here. I think these RC installer binaries should work for you. That will get you a cluster.
For OLM, I am not sure if there is a doc yet, but you can follow these instructions to load in the offline catalog. This process will get better for 4.3.
In your Operator, you should support the ability to pass in a registry hostname and path to an image, should someone want to import your required operand images, similar to the catalog experience. For example, this is a MariaDB CR:
apiVersion: charts.helm.k8s.io/v1alpha1
kind: Mariadb
metadata:
name: example-mariadb
spec:
image:
debug: false
pullPolicy: IfNotPresent
registry: docker.io
repository: bitnami/mariadbPlumb that all the way through into your code where you construct your StatefulSet or Deployment. Another example is Prometheus, which allows you to pass in args for the images that it uses.
- blocks
-
KOGITO-1235 Kogito Operator Productization
- Closed
- duplicates
-
KOGITO-554 Follow up with operator disconnect install for OCP 4.2
- Closed