bitsofinfo

Bret - yes have read your blog post previously and appreciated that work and post you made, it was a good read. Glad to hear your insights and it sounds...

Nothing in particular I need to see, would just be good for Docker to at least have one that declares what is being worked on w/ swarm, goals, new features...

Some longstanding issues would be nice to see on a roadmap https://github.com/moby/moby/issues/26259 https://github.com/moby/moby/issues/35082 https://github.com/moby/moby/issues/25885 https://github.com/moby/moby/issues/25526 https://github.com/moby/moby/issues/25303 https://github.com/moby/moby/issues/23880 https://github.com/moby/moby/issues/38162 https://github.com/moby/moby/issues/31923 https://github.com/docker/swarmkit/issues/2737

https://github.com/moby/moby/issues/39447

I'd say no; a blog post and one issue is not a roadmap

also agree with the note in the op about non-firing conditions being flagged as the color red. Makes it a bit misleading. different icons or "look" for conditions to differentiate?

any rough eta when this feature might be out? everyone on my team that sees the dashboard, gets immediately confused by the red/green, where the red is just "conditions" "failures"

/remove-lifecycle stale

/remove-lifecycle stale

I sometimes use literal keys w/ dots (i.e. think k8s labels are common usage of this) `"some.label.name": "label-value"` but I do have cases where i needed to set (via `--set-values`)...