Description of problem: Some customers would like the ability to change the cookie name for an application.
I assume this is referring to the cookie set by the router that is used for affinity? I'm not sure why they'd want to change that name. Can you give some use cases for when that is necessary?
Tracked by https://trello.com/c/dZpU26W9
origin PR 16454 openshift/origin: Pull Request 16454 openshift/openshift-docs PR 5309 openshift/openshift-docs: Pull Request 5309
openshift-docs PR 5309 MERGED
ON_QA to test against latest ocp-3.7 rc build.
verified in openshift v3.7.7, user can set default cookie name via ENV "ROUTER_COOKIE_NAME" for haproxy router as well as via annotation "router.openshift.io/cookie_name" for individual routes (including unsecure, edge and reencrypt route)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3464