Lee Briggs

Thanks! If there's anything we can do help, let me know.

Duplicate of #167

This is a tricky problem as mentioned in #965 and I'm open to ideas about solutions. For those not following, this is a downstream consideration with kubectl apply and has...

I don't actually know how we would be able to switch away from the declarative object configuration. The Kubernetes [imperative management](https://kubernetes.io/docs/concepts/overview/working-with-objects/object-management/#imperative-commands) has no knowledge of the previous state so it...

> check diff against statefile Sorry if it wasn't clear, that's largely what I meant by saying "import the state". This is a large amount of logic to implement for...

That's totally understandable. It's not clear how we work around this upstream limitation at this time, due to how we actually perform the apply logic.

Could you please share the diff you get before this error surfaces?

If you rebase the Dockerfile, I'm happy to merge this as yours is better

Sorry to nitpack. Couple things: The docker build stuff is now automated by goreleaser, so probably don't need that in the Makefile. It'd be good to keep the WORKDIR outside...

So, couple things. 1) the rekey endpoint seems to be unauthed. Anyone can start a rekey, which is nice. 2) we only need to submit to 1 vault in a...