Timothy Perrett

Is this assuming we'd have a field in the configuration file? If so, this seems fairly doable and would be a small change.

Think this has been gazumped by #223 - WDYT?

Firstly, thanks for writing up this great explanation; its a good jumping off point for us to get some kind of discussion and work started on this much-needed feature. The...

To update this thread on where i'm at with my thinking: presently devising a scheme to integrate https://github.com/turbinelabs/rotor into Nelson, so that we get the control plain and service discovery...

@stew sure. The simplest rotor implementation is where you have a central Rotor that does service discovery (based on k8s labels, not dissimilar to what was proposed above by @adelbertc),...

@goedelsoup can you flesh out what you want to see here? I'm not sure how we can expose this without inadvertently coupling consul and the manifest spec.

Once I fix something with my install I’ll test this out - it should work but I’m a little worried about the docker client compatibility

Without a dedicated maintainer for this feature I don’t think it will land. The biggest problem we have is that nobody actively involved in Nelson development is able to verify...

@adelbertc i've made a good start on porting the install docs: https://getnelson.io/getting-started/install.html - tagged you at the bottom there to fill out the k8s part.

On the whole, looks fine - address the couple of comments and i'd be happy to merge it.