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

Adding session affinity support through loadbalancer distribution type #730

Merged
merged 1 commit into from
Nov 4, 2019

Conversation

elweb9858
Copy link
Contributor

Adding session affinity support through loadbalancer distribution type

@elweb9858 elweb9858 force-pushed the distributiontype branch 2 times, most recently from 9fa369f to f2c56b3 Compare October 30, 2019 18:12
@jterry75
Copy link
Contributor

@nagiesek - PTAL

@jterry75
Copy link
Contributor

jterry75 commented Nov 4, 2019

@elweb9858 - Can you rebase squash these and we can take it?

Copy link

@erfrimod erfrimod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@ksubrmnn
Copy link
Contributor

ksubrmnn commented Nov 4, 2019

lgtm

@jterry75 jterry75 merged commit d9dd88b into microsoft:master Nov 4, 2019
@elweb9858
Copy link
Contributor Author

@jterry75 can you make a new release of hcsshim with this change?

@jterry75
Copy link
Contributor

jterry75 commented Nov 6, 2019

We dont typically do that. Why cant you vendor the commit you need?

@ksubrmnn
Copy link
Contributor

ksubrmnn commented Nov 6, 2019

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?

@jterry75
Copy link
Contributor

jterry75 commented Nov 6, 2019

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?

@ksubrmnn
Copy link
Contributor

ksubrmnn commented Nov 6, 2019

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

@elweb9858
Copy link
Contributor Author

@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?

@PatrickLang
Copy link

PatrickLang commented Nov 16, 2019

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants