Closed alisterz closed 3 years ago
Sticky sessions should be configurable via values.yaml and optional.
intention was to have it enabled by default so when ppl scale up GW, Policy Manager still works.
Is there a way to enable it only for like 9443 port instead for all server ports?
I agree with @Gazza7205 here. This needs to be optional and configurable via values.yaml, if customer wants to keep a closed environment they should be able to keep it that way for security purposes.
Description of the change Current Gateway chart doesn't not have sticky session enabled, which causes timeout issue when using Policy Manager with scaled (>2 pods) gateway deployments
Benefits
Allow Policy Manager continue to work even when Gateway is scaled to multiple pods, no more timeout issues.
Drawbacks N/A
Applicable issues N/A
Additional information Identical approach Portal charts are using.
Checklist
Chart.yaml
according to semver.[charts/gateway]
)values-production.yaml
apart fromvalues.yaml
, ensure that you implement the changes in both files