jdef
jdef
We're not yet cutting kubernetes-mesos releases from kubernetes/kubernetes. Please try building from our latest stable release https://github.com/mesosphere/kubernetes/tree/v0.7.1-v1.1.3.
they likely have. the current stable release in mesosphere/kubernetes is both heavily patched and tested. k8sm built from release-1.1 on kubernetes/kubernetes is neither. please test the stable release branch to...
I don't remember seeing that particular issue before. That said, there are quite a few code changes between the release 1.1 branch and our stable branch. Some things that come...
any luck with testing on the stable branch? On Wed, Jan 13, 2016 at 1:08 PM, Sanjana J Bhat [email protected] wrote: > There are no errors in the log files....
FWIW there's a new v0.7.2-v1.1.5 tag on the release-v0.7-v1.1 branch .. if this isn't working for you yet, you might try testing again with the updated code. the mechanism by...
DCOS-2302 looks the most relevant. not linking here since JIRA is an internal system On Tue, Dec 8, 2015 at 10:38 AM, Dr. Stefan Schimanski < [email protected]> wrote: > @jdef...
@mwasn it probably makes sense to have a k8s epic that links to this DCOS ticket.
assigned to Marcus, needs internal JIRA ticket
this is very useful for customers that want to statically allocate a port range for use by kubernetes (node ports, proxy ports, etc)
clarification: the kube proxy port range is not for node ports, but for ports allocated by the userspace proxy impl of kube-proxy. the stock k8s implementation uses port 0 to...