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.

Sign up for GitHub

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

Jump to bottom

rebase issues #8464

Closed
deads2k opened this issue Apr 11, 2016 · 6 comments
Closed

rebase issues #8464

deads2k opened this issue Apr 11, 2016 · 6 comments
Assignees
@mfojtik
Labels
priority/P3
Milestone
1.3.0

Comments

@deads2k
Copy link
Contributor

deads2k commented Apr 11, 2016 •
edited
Loading

scratchpad for me to keep track of problems as I go.
@deads2k deads2k added this to the 1.3.0 milestone Apr 11, 2016
@timothysc
Copy link

on 1.3 rebase, we will need to change the defaults that upstream sets for the kubelets.

--pods-per-core=10
--max-pods=255
xref: kubernetes/kubernetes#25813

We will have benchmark automation in place shortly.

/cc @rrati @jeremyeder

@deads2k
Copy link
Contributor Author

deads2k commented May 19, 2016

@mfojtik I think this now yours.

@jeremyeder
Copy link
Contributor

Awesome! Oh, wasn't the max 254? (openshift-sdn starts handing out IPs at x.x.x.2 within the per-node network segment).

@timothysc
Copy link

Max on 3.2 is currently 510

@jeremyeder
Copy link
Contributor

@mpbarrett

@timothysc
Copy link

So setting these defaults fell through the cracks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mfojtik mfojtik

Labels
priority/P3
Projects
None yet
Milestone
1.3.0
Development

No branches or pull requests
5 participants
@mfojtik @timothysc @jeremyeder @0xmichalis @deads2k