-
Notifications
You must be signed in to change notification settings - Fork 264
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
Adding session affinity support through loadbalancer distribution type #730
Conversation
6e88454
to
a69c8c2
Compare
9fa369f
to
f2c56b3
Compare
@nagiesek - PTAL |
339248f
to
3ac31cb
Compare
@elweb9858 - Can you rebase squash these and we can take it? |
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.
Looks good.
3ac31cb
to
c5f8692
Compare
lgtm |
@jterry75 can you make a new release of hcsshim with this change? |
We dont typically do that. Why cant you vendor the commit you need? |
I imagine the Kubernetes work won’t be completed before code freeze on the 17th anyway. So we do have some time for this. We get a lot of pushback when we try to vendor in hcsshim without a release. There have been a few changes in the hcn code, and there hasn’t been a release since early February. Can we get a timeline for the next release? |
We don't make (and have never made) tagged releases for anything but Docker and we cant specifically tag just the hcn package. @PatrickLang - I thought we decided Kubernetes was ok with this since we are a vendor only release and not a binary? |
To clarify, we don’t expect hcn to be versioned. I understand it’s under the umbrella of hcs releases. Patrick will probably have all the context here, but I have personally seen pushback without a release. Though I’m sure we can still do it |
@jterry75 I'm trying to get this change vendored into kubernetes, but hcsshim's dependency on containerd v1.3.0 breaks other things in kubernetes, namely github.com/google/cadvisor/container/containerd, which depends on containerd v1.0.2. Any idea how I can work around this? |
@elweb9858 - I'd ask in the Kubernetes slack (invite @ slack.k8s.io), channel #k8s-code-organization . There are discussions around moving to modules and impacts on vendoring there https://kubernetes.slack.com/archives/CHGFYJVAN/p1573237770111000 |
Adding session affinity support through loadbalancer distribution type