Solace Pubsub+ Event Broker Operator is Now Available!

Options
shwetamazumder
shwetamazumder Member, Employee Posts: 6 Solace Employee
edited July 2023 in General Discussions #1

Solace Community,

I am excited to announce that Solace has launched its own Kubernetes Operator a.k.a Solace Pubsub+ Event Broker Operator , Version 1.0.0 and it is available at https://github.com/SolaceProducts/pubsubplus-kubernetes-quickstart.

Pubsub+ Event Broker Operator makes event broker deployment declarative in a kubernetes cluster , hence making it easy for users to perform operational tasks.

The Operator is free to use . Below are the features covered in first release:

  • Installing a PubSub+ Software Event Broker in non-HA , HA or dev mode.
  • Adjusting the deployment to updated parameters (with limitations).
  • Upgrading to a new broker version.
  • Repairing the deployment.
  • Enabling Prometheus monitoring.
  • Providing status of the deployment.

Check out my video to see the Operator in action at https://solace.com/resources/videos/pubsub-event-broker-deployment-in-kubernetes-cluster

Stay tuned for many more exciting feature releases in the Operator. 😎


Cheers!

Shweta Mazumder , Product Manager

Tagged:

Comments

  • leoxucn
    leoxucn Member Posts: 2
    Options

    Hello I use this to deploy the operator to start event broker in Kubernetes 1.28.3, but it failed.

  • shwetamazumder
    shwetamazumder Member, Employee Posts: 6 Solace Employee
    Options

    What is the version of the broker you are deploying ?

  • leoxucn
    leoxucn Member Posts: 2
    Options

    I just follow up this link to deploy the operator, then build the event broker, there is no version mentioned for event broker.

    https://github.com/SolaceProducts/pubsubplus-kubernetes-quickstart

  • shwetamazumder
    shwetamazumder Member, Employee Posts: 6 Solace Employee
    Options

    Can you verify if the operator was installed correctly by watching the pod :
    # Wait for deployment to complete

    kubectl get pods -n pubsubplus-operator-system --watch

    If not, what is the error you are getting?