Felix Bünemann

The `walk_tree` method yields to a block, so how would you use previous/next in that context?

What would be an example use case for such a functionality?

Btw. you could model the `next` case with an enumerator on top of `walk_tree`: ```ruby enum = Enumerator.new do |y| Foo.walk_tree do |node, _| y

That would be much more efficient and easier to achieve with a nested set, because your previous node would be `current_node.lft - 1` and the next node would be `current_node.rgt...

There isn't really a straight-forward way to do this. The first problem you will have is that there isn't really a defined order of nodes, so if you have a...

Have you tried `order: :order` instead?

This behavior can easily inspected with: ``` kubectl get --namespace deis --show-all pods | grep build- ``` The number of completed pods will increase by one for each build.

I'm running K8s 1.4.x if that matters. Regarding #57 suggestion for Jobs – neither Jobs nor Pods are removed automatically. From the [K8s Job](https://kubernetes.io/docs/user-guide/jobs/#job-termination-and-cleanup) docs: > When a Job completes,...

Interestingly the docs on [Pod Lifecycle](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-lifetime) say: > In general, Pods do not disappear until someone destroys them. This might be a human or a controller. The only exception to...

I have opened kubernetes/kubernetes#41787 for clarification of the above statement from the docs.