Kent Rancourt

Tentatively. It's going to require some experimentation and design so that we land in a good place. For now, I'm relocating this issue to the main Brigade repo.

Probably worth noting here that I've been working on something like this-- and it's based on an open specification (which is only a draft right now). The spec is here:...

@arschles yes. https://github.com/lovethedrake/devdrake can execute pipelines locally using nothing more than the local Docker daemon under the hood-- no k8s involved even.

Per the [2.0 proposal](https://github.com/brigadecore/brigade/tree/master/2.0-PROPOSAL#job-sidecars), 2.0 will drastically improve support for alternative workers, but introducing new (official) ones is deferred to a subsequent 2.x release. For now, I'm dropping the 2.0...

Now that v2.0.0 is out, I am going to start revisiting this as time permits. Some effort has previously gone into an open specification for declarative pipelines, but it hasn't...

@AnuragThePathak I've been told that [this](https://github.com/cncf/mentoring/discussions/602) is the official place for discussing this.... I'll copy your question over to there and answer there also.

Ah. Thanks for the clarification @nate-double-u. If it's all the same, I'm going to keep directing people there regardless because it's easier for me to keep the discussions consolidated instead...

I'm second-guessing the extent to which this is needed. Let me get back to you on the great questions above.

@vdice after thinking about this more, I do still think we should do it. My rationale is that if the default setup involves SSL and auto-generated certs to secure communication...

> I'm hesitant to tackle an overhaul of the brig config file for this feature We agreed in an offline conversation that this is actually out of scope. Noting that...