Round-robin Routing for Specific Path in Kubernetes Service for Drools Rule Management

[cherrycharan]

We need to implement round-robin routing for a specific path in our Kubernetes service that manages Drools rules. The goal is to ensure that subsequent requests to this particular URL always hit different pods in the service, thus distributing the load evenly across available pods.

The current setup directs all requests to a single pod based on the existing Kubernetes service configuration. We would like to modify this behavior only for a specific path (e.g., /drools-rule) and ensure that each new request for this path gets routed to a different pod.

Key requirements:

1. Implement round-robin load balancing for the /drools-rule path.
2. Ensure the rest of the application continues to use the existing load-balancing strategy.
3. Requests for the same session or user should not impact the distribution logic; it should always hit different pods.
4. This should work seamlessly with our current ingress and service configuration.

Please advise on how we can configure Kubernetes or make adjustments to the service to achieve this, or if we need to modify our ingress setup or use specific annotations.