v3.9.0

Release 3.9.0

New Features

• For production environments, we now recommend configuring the admin password using an existing Kubernetes secret rather than specifying it in plain text in your Helm values

Notes

• The secret key must be named username_admin_password (this is a required convention)
• The secret must exist in the same namespace as the deployment
• This configuration is strongly recommended for production environments
• Existing deployments using plain text passwords can be migrated to use secrets

v3.8.0

Release 3.8.0

New Features

• System Scaling Parameters: Added support for new system scaling configuration options to optimize performance and resource allocation:
  • maxKafkaBridgeCount - Configure maximum number of Kafka bridges
  • maxKafkaBrokerConnectionCount - Set maximum Kafka broker connection limit
  • maxBridgeCount - Define maximum number of bridges
  • maxSubscriptionCount - Control maximum subscription limit
  • maxGuaranteedMessageSize - Set maximum guaranteed message size

Updates

• Brand Alignment: Updated style guide to ensure consistency with new branding standards

Configuration

The new scaling parameters can be configured under solace.systemScaling in your values file. For reference, use the https://docs.solace.com/Admin-Ref/Resource-Calculator/pubsubplus-resource-calculator.html

v3.7.0

Added DMR cluster status check in the readiness check script.

v3.6.0

Added PubSub+ Insights functionality support.

Refer to public Solace documentation, INSIGHTS.md, and values.yaml for deployment and configuration options.

v3.3.4

Updates

• Removed prod100 from configuration setup and made prod1k the default
• Limit the CPU usage for prod1k to 1.5
• Updated documentation

v3.3.3

New Feature

• Added support for Tolerations and Node affinity

Improvements

• Document update to reflect changes of not needing solace.usernameAdminPassword for helm upgrade

v3.3.2

Improvements

• Redundancy down or config-sync down no longer impacts the readiness of the AD-Active broker in an HA deployment
• Fixed monitor verbose readiness check logging

v3.3.1

Improvements

• Documentation updates

v3.3.0

Improvements

• Liveness and Startup probes now work with DR if it is set up
• Fix for SEMP parsing error bug
• Updates and upgrades of dependencies

New Feature

• assert-master migration to assert-leader

v3.2.0

Improvements

• Readiness check reliability improvements
• Config-sync improvements in High Availability mode
• Readiness check clearer logging

New Feature

• Added PodDisruptionBudget for Broker nodes in High Availability mode

Closes #107