feat: remove sticky cookie config from uplinks#347
Merged
Conversation
The sticky session affinity configuration is no longer needed on the Uplink CRD. This removes the UplinkSticky and UplinkCookie types, their generated deepcopy methods, CRD manifest entries, and associated tests.
komalsukhani
approved these changes
Mar 9, 2026
youkoulayley
approved these changes
Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The sticky session affinity configuration is no longer needed on the Uplink CRD. A child cluster can have only one address, therefore adding sticky configuration on the service has no impact. When cluster affinity is needed, a sticky configuration needs to be added in a
weightedservice before.This is not a breaking change. The Uplink CRD is not yet used by a released version of Traefik Hub.