-
Notifications
You must be signed in to change notification settings - Fork 880
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
Feat: add externalTrafficPolicy support #626
Conversation
- externalTrafficPolicy can be set for both the ui and server services. It is only supported for NodePort or LoadBalancer service types.
{{- end }} | ||
{{- end -}} | ||
|
||
{{/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function is mostly unrelated to this fix, so I am okay if we forgo it. I see we have at least one other PR that introduces another LB so it might be good to keep it?
Idea: there is a ton of Service definition duplication in this chart. It is possible that we could move most of the duplication to shared functions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good to me.
I wonder if there would be a case where folks would need to set different externalTrafficPolicy's for standby and active HA services?
Thanks!
Currently they all share the same service values, so I think setting the policy as is should be ok. We can probably update it when/if the need arises. |
- externalTrafficPolicy can be set for both the ui and server services. It is only supported for NodePort or LoadBalancer service types.
It is only supported for NodePort or LoadBalancer service types.