You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have a few salt masters behind a elastic load balancer with sticky sessions enabled. This configuration works fine for our clients the save and resent the cookies (resending the AWSELB cookie) to hit the same server for the duration of the cookie to get X-AUTH-TOKEN and handle multiple requests. Using this same configuration in Jenkins does not appear to handle this though. Requests coming from the plugin end up hitting multiple servers. Could you enhance the plugin to resend the cookies so sticky sessions on the load balancer can be used ?
The text was updated successfully, but these errors were encountered:
This sounds like a bit of a change from where things are today. At the moment, each connection to the salt-api uses a fresh http connection. I'll have to investigate what it would entail to re-use connections in order to retain headers.
We currently have a few salt masters behind a elastic load balancer with sticky sessions enabled. This configuration works fine for our clients the save and resent the cookies (resending the AWSELB cookie) to hit the same server for the duration of the cookie to get X-AUTH-TOKEN and handle multiple requests. Using this same configuration in Jenkins does not appear to handle this though. Requests coming from the plugin end up hitting multiple servers. Could you enhance the plugin to resend the cookies so sticky sessions on the load balancer can be used ?
The text was updated successfully, but these errors were encountered: