Rafael Schloming

Sorry for not being clearer, I'm not actually asking for documentation for the existing REST API. I was aware of that and for my purposes the existing kubernaut client is...

> While not "pretty" this is a simple work around for (1) `curl ... | python -c 'import sys, json; print json.load(sys.stdin)["claim"]["kubeconfig"]'` > That workaround isn't a super great option...

What might work here is some kind of option that would tell claim to wait a configurable time for the cluster to be released and then forcibly steal the claim...

Good point on (2), I hadn't thought about that. FYI, the main context for this is that I want to have an idiot proof way to avoid "leaking" resources from...

One problem to be aware of that people have run into with this strategy is that because haproxy is deployed with every client in this architecture, if you have say...

We are currently working on deployment with containers. We expect to deploy Sherlock and Watson inside the containers, but we may introduce another component on the host and/or modify Watson...

Thanks for taking the time to file this issue! I really like the idea of being able to have extremely minimal footprint outside of git, and it sounds like sops...

Sorry for the delay, this took a bit longer to swap into my brain than I expected. Also, apologies for the long post, but I haven't yet figured out a...

@mumoshu That sounds like a reasonable idea to me. At least worth a try.

@blak3mill3r As you say, I suspect having the container actually depend on the manifests would be pretty unusual, but if that ever comes up we could probably make it configurable,...