🚢 New Helm Templates for Particular Platform Now Available

Feedback welcome!

We’re pleased to share that we’ve released new Helm template examples to help you deploy the Particular Platform—including ServiceControl, ServiceControl.Audit, ServiceControl.Monitoring, and ServicePulse—on Kubernetes with greater ease and flexibility.

These charts support a wide range of customizations and come with sensible defaults to get you started quickly. You can:

  • Spin up a new environment with a single command
  • Configure audit instances with multiple queues to support competing consumers or sharding of audit queues
  • Configure audit and error instances to have dedicated database connections
  • Deploy to production with full license support and custom values.yaml overrides
  • Use advanced setup and configuration options such as ingress, custom probes, and affinity rules

:package: Docker images are pulled from the same repositories we’ve made available as part of our Linux container support.

:hammer_and_wrench: Get started
Visit the Helm chart README for examples and instructions.

:speech_balloon: We’d love your feedback
We’re actively looking for input from early adopters to improve the experience. If you’re using Kubernetes and want to simplify your platform deployments, give these templates a try and let us know what works well—or what could be better.

Drop your questions, suggestions, or findings right here in this thread. We’ll be listening closely and using your feedback to guide future updates.

Thanks for helping shape the future of the Particular Platform on Kubernetes!

The Team in Particular

1 Like

Hi @danielmarbach ,

very interesting. Thank you for posting.
I’d like to use helm to deploy the particular platform in the future and therefor looking at your mentioned repository. I’m just a little irritated by the name. The helm chart lives in an “PlatformContainerExamples” repository? Are those charts maintained and ready to be used - or are they just examples? Am I expected to write my own charts according to the examples?

The readme mentiones that RavenDB should be installed separately. The documentation says that there is a specific RaveDB image that should be used in the same version as the other particular container images. Then why is it not part of the helm chart? This would make it very easy to use and could easily be kept in sync with the other image versions.

It would be really great to have a maintained helm chart that is ready to use including the database. (Similar to the installers today - they also bring everything that is needed without me having to care about the database separately).

Thanks for your insights and best regards,
Philipp