1. Documentation
2. 2024.1 (Latest) 2024.0 10.3 10.2 10.1 10.0 9.10 9.9 9.8 9.7 9.6 9.5 9.4 9.3 9.2 9.1 9.0 8.2 8.1 8.0 7.6
3. Deployment
4. Kubernetes templates

Kubernetes templates

Our Docker Images are ready to deploy to any Kubernetes Cluster. We tested our example configurations with these Kubernetes services:

• Amazon Managed Kubernetes Service (Amazon EKS)
• Azure Kubernetes Service (AKS)
• MiniKube
• MicroK8S

To deploy one of our Kubernetes templates, click Download to download the template files, or select a link for additional details.

• [Download] for generic production purposes
• [Download] for High Availability
• [Download] for production deployments that need easy Hadoop connectivity
• [Download] for production deployments that need low-latency scoring capability

For each template, we provide:

• the proposed volume definitions, where you can adjust the storage size required by the component
• the service definitions, which are either internal services used by other services (e.g. the database service) or external ones (e.g. RapidMIner Server Web UI), that are exposed to the users.
• the deployment configurations that are container definitions very similar to the ones used in the docker-compose templates, also including the required environment variables.

You can mix and match these templates if you need to produce a custom deployment, e.g. if you need a production deployment that has both Real-Time Scoring and Hadoop Connectivity capabilities.

See also: Services and locations provided by these templates

Instructions for Kubernetes deployments

1. Make sure that the connection to your Kubernetes cluster is working

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

2. Create and check the volumes

$ kubectl apply -f volumes.yaml
persistentvolumeclaim/pgvolume-claim created
persistentvolumeclaim/rmsvolume-claim created
$ kubectl get pv pvc
$ kubectl get pv pv

3. Create and check services

$ kubectl apply -f services.yaml`
service/rapidminer-server-amq-svc created
service/postgres-svc created
service/rapidminer-server-svc created
$ kubectl get svc
NAME                        TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
postgres-svc                ClusterIP      10.152.183.3             5432/TCP         72s
rapidminer-server-amq-svc   ClusterIP      10.152.183.128           5672/TCP         72s
rapidminer-server-svc       LoadBalancer   10.152.183.252   ******        8080:30661/TCP   72s

4. Deploy services

$ kubectl apply -f database.yaml
pod/database created
$ kubectl apply -f rapidminer-server.yaml
pod/rapidminer-server created
$ kubectl apply -f job-agent.yaml
deployment.apps/job-agent created

5. Check the running PODs

$ kubectl get pod
NAME                                          READY   STATUS    RESTARTS   AGE
pod/database                                  1/1     Running   0          41m
pod/job-agent-556b49567b-5cm8n                1/1     Running   0          44s
pod/job-agent-556b49567b-6585h                1/1     Running   0          44s
pod/job-agent-556b49567b-zk44g                1/1     Running   0          44s
pod/rapidminer-server                         1/1     Running   0          40m

Services and locations

Once the deployment is running, the configured reverse proxy listens on the standard HTTP (80) port by default and if a HTTPS certificate is configured then on the HTTPS (443) port also. The following locations are available on the deployment public URL (depending on the list of the deployed services).

The initial login credentials are set in the .env file (KEYCLOAK_USER and KEYCLOAK_PASSWORD variables). By default you can login using the username "admin" and password: "changeit".

To learn more about the used technologies and how to operate and administer your platform deployment, see our technology overview page.