The quick-start guide explains how to use the operator to deploy a default persistent cluster. As a result, you should have a running cluster that operates within the most recent GridGain Community Edition version. The steps are described as simple as possible. The quick-start guide does not contain much technical details, please refer to the Operator Configuration for more information.
For this quick-start guide, your Kubernetes cluster is assumed to have a default dynamic storage provisioner. However, a storage class can be specified manually.
Create the operator namespace.
kubectl create namespace apache-ignite-operator
kubectl apply -f https://gg-operator.s3.eu-central-1.amazonaws.com/crds.yaml
Deploy the operator.
kubectl apply -f https://gg-operator.s3.eu-central-1.amazonaws.com/default_ignite_operator.yaml -n apache-ignite-operator
kubectl get pods -n apache-ignite-test -w
NAME READY STATUS RESTARTS AGE apache-ignite-test-cluster-0 1/1 Running 0 1m apache-ignite-test-cluster-1 1/1 Running 0 1m
Access Control Center integration.
Default stateful set is preconfigured to include all necessary libraries for accessing Control Center, which is free and cloud-based. If your environment can access external websites, then, after the pods are running, you can find the connection link to the Control Center. The link expires within five minutes.
kubectl logs apache-ignite-test-cluster-0 -n apache-ignite-test | grep https://control.gridgain.com/clusters