decisions service configuration in production
I have question on configuring the decisions service in aks, do we need to use LoadBalancer with sessionAffinity (which usually used for stateful service rather than restful service).
We are currently have service manifest configured and I guess we made it earlier to expose the service to public and get it assigned public IP so we can test it,
However in the official documentation the service is configured with type: ClusterIP
Would you please advice on what’s the correct way to configure decisions service in production,
Comments
-
Correct. AKS servers should have type set to ClusterIP. Then cookie-based-affinity should be added in the YAML and set to true.
Howdy, Stranger!
Categories
- 4.4K All Categories
- 86 General
- 13 Training
- 212 Installation / Setup
- 1.2K Flows
- 112 Rules
- 282 Administration
- 216 Portal
- 501 General Q & A
- 719 Forms
- 353 Reports
- 3 Designer Extensions
- 48 Example Flows
- 58 CSS Examples
- 1 Diagram Tile
- 8 Javascript Controls
- 189 Pages
- 5 Process Mining
- New Features
- 187 Datastructures
- 71 Repository
- 233 Integrations
- 30 Multi-Tenant
- 27 SDK
- 81 Modules
- 60 Settings
- 27 Active Directory
- 12 Version 7
- 36 Version 8
- 143 Lunch And Learn Questions