jdef
jdef
Actually, I shouldn't have said "... which k8s-mesos doesn't currently support". It looks to me like the connection is being made to the apiserver, which is a stock k8s component....
@sanjana-bhat Out of curiosity, are you doing this on DCOS or on some other mesos cluster?
Nevermind, I see that you indicated upstream_k8sm. BTW that branch is pretty unstable. I actually just removed all of the Go code and build files. If you want the latest...
Yeah, but the upstream_k8sm version of that, which basically says to: ``` shell export KUBERNETES_CONTRIB=mesos ``` ... and then follow the k8s guide for building k8s binaries by hand. In...
Yes, that's correct: all future code changes will happen upstream.
re-opening this so that we don't lose track of it. we'll want to make sure that this works with DCOS
TODO: re-test this now that initial TLS support has landed
Bringing this up because there's a disparity between published services, which are implemented by the `proxy` process and exposed container ports via docker default networking: - proxy listens on `:::$servicePort`...
This needs another look. The ground has shifted significantly since this was last investigated
i'm fine with this as a stretch goal for MVP On Tue, Jan 5, 2016 at 1:34 PM, Dr. Stefan Schimanski < [email protected]> wrote: > @jdef https://github.com/jdef this is more...