Skip to main content
Starting March 31st, 2024, access to the StreamNative Pulsar distribution will require a valid StreamNative subscription. As a result, StreamNative Pulsar images such as streamnative/private-cloud, streamnative/sn-platform and streamnative/sn-platform-slim will require a license key to run; otherwise, the component will fail to start. For StreamNative Private Cloud users, the license key for sn-operator can also be used for the StreamNative Pulsar images. The sn-operator automatically activate the StreamNative Pulsar images with the imported license key. This documentation provides comprehensive guidance on migrating to StreamNative Pulsar images.

Prerequisites

  • For Pulsar Operators users, you need to follow Upgrade from Pulsar Operators to shift the StreamNative Operator.
  • sn-operator chart: 0.1.1 or higher

Migrate to StreamNative Pulsar images

Migrate from CRD manifests

Create a PulsarCoordinator manifest:
Add k8s.streamnative.io/coordinator-name label on ZooKeeperCluster, BookKeeperCluster, PulsarBroker and PulsarProxy manifests:
After applying these configurations on your manifests, you should see a Secret called private-cloud-sn-license under your Kubernetes namespace. This Secret will be mounted by your Pulsar cluster to activate.

Migrate from StreamNative Platform Chart

Create a PulsarCoordinator manifest, and the PulsarCoordinator object’s metadata.name should be same with the PulsarBroker object. You can run below commands to get the PulsarBroker object name:
After getting the PulsarBroker object name, Create the PulsarCoordinator like below:
Add k8s.streamnative.io/coordinator-name label on zookeeper.zooKeeperCluster.labels, bookkeeper.bookKeeperCluster.labels, broker.pulsarBroker.labels and proxy.pulsarProxy.labels:
After updating configuration, run the helm upgrade to update your StreamNative Platform.