Darren Shepherd

@hikhvar Are the examples of must have features that are provided through annotations. One of the tricky things is that we want to ensure that the Acornfile stays infrastructure agnostic...

We don't have all the parameters for logs, we will add more. Right now we basically just have `-f`.

Yes, this absolutely will come. The design of acorn is such that all network communication paths are known and have some logical boundary. We will either be generating network policies...

Researching this a bit, network policies would be extremely simple. LInkerd looks straight forward too and Istio is rocket science like normal. So we will start with NetworkPolicies and go...

@cloudnautique What is the persistentVolumeReclaimPolicy of the existing PV? We need that to be "Retain", maybe we don't update it, I thought we did.

There's a way to do this but you need an acorn of acorns. I'll explain after the meetup. This stuff is undocumented, because again, on the fence about this stuff.

Oh wait, there isn't. Okay, let me think about how this can be done.

That can we done with a jobs and dependsOn ```cue containers: { app: { image: "foo" dependsOn: "db-migrate" } } jobs: { "db-migrate": { image: "foo" entrypoint: "bundle exec rails...

Correct, that's the behavior.

The only time the job will run again is if the definition of the job changes. This is important because if you update your app and you need to "rerun"...