Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCI Network Loadbalancer only supports sessionAffinity: None for v0.20.0 #155

Closed
atomic-tang opened this issue Sep 2, 2024 · 2 comments
Closed
Labels
priority: high type: bug Something isn't working
Milestone

Comments

@atomic-tang
Copy link

Description

Upgraded to version 0.20.0 with helm on OCI but the network loadbalancer failed to start up due to the following error:

Error syncing load balancer: failed to ensure load balancer: invalid service: OCI only supports SessionAffinity "None" currently

Other loadbalancers on OCI cannot be used as they do not support UDP traffic.

@rg0now rg0now added priority: high type: bug Something isn't working labels Sep 2, 2024
@rg0now
Copy link
Member

rg0now commented Sep 2, 2024

Guess we'll have to add yet another Gateway annotation to optionally disable client affinity. That being said, the policy of OKE to straight our reject an LB Service using a feature that's been GA for I don't know how many Kubernetes releases is at least questionable I'd say.

@rg0now
Copy link
Member

rg0now commented Sep 20, 2024

Could you please make a quick test to check whether the fix solved your problem? Just add the annotation stunner.l7mp.io/disable-session-affinity: true to your Gateway, this would revert the LB Service session affinity setting to None. Hopefully this will make OCI happy.

Feel free to reopen if something new shows up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants