Install the Serverless Logic Operator
This guide describes how to install the Serverless Logic Operator in a Kubernetes or OpenShift cluster. The operator is in an early development stage (community only) and has been tested on OpenShift 4.12+ and Minikube.
-
An OpenShift cluster with admin privileges. Alternatively, you can use Minikube or KIND.
-
kubectl
command-line tool is installed. Otherwise, Minikube provides it.
OpenShift Serverless Logic Operator OpenShift installation
To install the operator on OpenShift refer to the "Adding Operators to a cluster" from the OpenShift’s documentation.
When searching for the operator in the Filter by keyword field, use the word Serverless Logic
. If you’re installing from the CLI, the operator’s catalog name is logic-rhel8-operator
.
Uninstall
To remove the operator on OpenShift refer to the "Deleting Operators from a cluster" from the OpenShift’s documentation.
OpenShift Serverless Logic Operator Kubernetes installation
To install the operator on Kubernetes refer to the "How to install an Operator from OperatorHub.io" from the OperatorHub’s documentation.
When searching for the operator in the Search OperatorHub field, use the word sonataflow
.
Uninstall
To remove the operator on Kubernetes follow the document "Uninstall your operator" from the OLM’s documentation.
When searching for the subscription to remove, use the word my-sonataflow-operator
.
OpenShift Serverless Logic Operator Manual Installation
If you’re running on Kubernetes or OpenShift, it is highly recommended to install the operator from the OperatorHub or OpenShift Console instead since the installation is managed by OLM. Use this method only if you need a snapshot version or you’re running locally on Minikube or KIND. |
Prepare a Minikube instance
You can safely skip this section if you’re not using Minikube. |
-
A machine with at least 8GB memory and a CPU with 8 cores
-
Docker or Podman installed
Run the following command to create a new instance capable of installing the operator and deploy workflows:
minikube start --cpus 4 --memory 4096 --addons registry --addons metrics-server --insecure-registry "10.0.0.0/24" --insecure-registry "localhost:5000"
To speed up the build time, you can increase the CPUs and memory options so that your Minikube instance will have more resources. For example, use |
If Minikube does not work with the default driver, also known as docker
, you can try to start with the podman
driver as follows:
minikube start [...] --driver podman
Install
To install the OpenShift Serverless Logic Operator, you can use the following command:
kubectl create -f https://raw.githubusercontent.com/kiegroup/kogito-serverless-operator/9.99.x-prod/operator.yaml
You can also specify a version:
kubectl create -f https://raw.githubusercontent.com/kiegroup/kogito-serverless-operator/<version>/operator.yaml
<version>
should be 9.99.x-prod
.
You can follow the deployment of the OpenShift Serverless Logic Operator:
kubectl get pod -n sonataflow-operator-system --watch
A successful installation should have an output like this:
NAME READY STATUS RESTARTS AGE
sonataflow-operator-controller-manager-948547ffd-sr2j2 0/2 ContainerCreating 0 6s
sonataflow-operator-controller-manager-948547ffd-sr2j2 1/2 Running 0 7s
sonataflow-operator-controller-manager-948547ffd-sr2j2 2/2 Running 0 20s
You can also follow the operator’s log:
kubectl logs deployment/sonataflow-operator-controller-manager -n sonataflow-operator-system -f
Once the operator is running, it will watch for instances of the OpenShift Serverless Logic Custom Resources (CR). Using CRs, you can configure your OpenShift Serverless Logic environment and define Workflows and builds to be handled by the operator.
Uninstall
To uninstall the Serverless Logic Operator, first, you must delete all the OpenShift Serverless Logic Custom Resources (CR) instances managed by it. Once the CRs are deleted, you can then delete all resources created during the operator installation.
To delete every CR managed by the operator in your cluster, you can run these series of commands:
kubectl delete --all workflow --all-namespaces
kubectl delete --all sonataflowbuild --all-namespaces
kubectl delete --all sonataflowplatform --all-namespaces
Alternatively, if you created everything under the same Namespace, deleting the given namespace has the same outcome.
To uninstall the correct version of the operator, first you must get the current version by running:
kubectl get deployment sonataflow-operator-controller-manager -n sonataflow-operator-system -o jsonpath="{.spec.template.spec.containers[?(@.name=='manager')].image}"
$registry.redhat.io/openshift-serverless-1-tech-preview/logic-rhel8-operator:$1.32.0
kubectl delete -f $https://raw.githubusercontent.com/kiegroup/kogito-serverless-operator/9.99.x-prod/operator.yaml
Found an issue?
If you find an issue or any misleading information, please feel free to report it here. We really appreciate it!