Skip to main content

Prerequisites

To use StreamNative Private Cloud, the following are required:
  • Prepare a Kubernetes cluster (Kubernetes version >= 1.16).
  • Install kubectl (v1.16 or above), compatible with your cluster (+/- 1 minor release from your cluster).
  • Install Helm (v3.0.2 or above).

Create the operators namespace

  1. Create a Kubernetes namespace where the operator will be installed later.

Install StreamNative Private Cloud

Import license

Before installing StreamNative Private Cloud, you need to import a valid license. Otherwise, StreamNative Private Cloud will stop reconciling with a “no valid license” error message:
If you do not have any license, you can contact StreamNative to apply for a free trial. When you have a license in hand, you can import it through:
metadata.labels with the cloud.streamnative.io/type: "license" is required because the sn-operator will detect secrets in its namespace with label and to import automatically.

Install the StreamNative Operator

  1. Add the StreamNative chart repository.
  2. Deploy the StreamNative Operator using the sn-operator Helm chart in the created Kubernetes namespace. Cluster-scoped installation (default) By default, the operator is installed with cluster-wide scope and watches for Pulsar resources across all namespaces:
    In this mode, the operator creates ClusterRole and ClusterRoleBinding resources to manage Pulsar clusters in any namespace. Namespace-scoped installation Alternatively, you can restrict the operator to watch only specific namespaces. This creates Role and RoleBinding resources instead of cluster-level permissions:
    In namespace-scoped mode, the operator will only reconcile Pulsar resources in the specified namespaces. Multiple namespaces should be comma-separated with escaped commas (\,) in the Helm command.
  3. Verify that Operator Pods are running.

Create the Pulsar namespaces

Create the namespaces pulsar. The pulsar namespace is used for deploying your Pulsar cluster.

Provision a Pulsar cluster

To provision a Pulsar cluster through the StreamNative Operator, you need to define a YAML file for your Pulsar cluster.

Choose a metadata store

The default quick start uses ZooKeeperCluster for Pulsar metadata.

Tools usage

StreamNative Private Cloud provisions a toolset Pod which packages regual Pulsar tools:
Use pulsar-client to quickly produce some messages
Use pulsarctl to check the resource status

Access to Console

Clean up

Run the command below to delete your Pulsar cluster.
Run the command below to remove the sn-operator.