Solace Community is getting a facelift!
On March 3rd we will be starting the process of migrating Solace Community to a new platform. As a result, Solace Community will go in to a temporary read-only state. You will still be able to come onto Solace Community and search through posts to find answers, but you won't be able to ask questions, post comments, or react in any way.
We hope to have the migration complete by Wednesday March 5th (or sooner), so please keep an eye out!
Solace Pubsub+ Event Broker Operator is Now Available!
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
Comments
-
What is the version of the broker you are deploying ?
0 -
Can you verify if the operator was installed correctly by watching the pod :
# Wait for deployment to completekubectl get pods -n pubsubplus-operator-system --watch
If not, what is the error you are getting?0