4 ms·
This is great work! Even with just a few dozen CRDs kubectl can get a little slow on versions prior to these changes. I am excited about crossplane because han
by CleverLikeAnOx 4y ago
This is great work! Even with just a few dozen CRDs kubectl can get a little slow on versions prior to these changes.
I am excited about crossplane because handling infrastructure via a reconciliation loop addresses most of my problems with terraform. Namely, managing/sharing a state file, importing resources that already exist, and ensuring that reality doesn't drift from terraform state.
- theptip 4y agoI do like this direction. What's the current state of the art for rendering the diffs? E.g. in Terraform your `terraform plan` will show whether the change requires a delete/create or just an edit. Naively, if I just look at the raw CRD diff, that information won't be apparent.
- negz 4y agoWe've thought about a client-side tool to diff desired from most-recently-observed actual state, similar to tf plan. Nothing built yet though. FWIW though we never automatically delete-and-recreate in Terraform fashion. Our thinking is that once Kubernetes supports it (or once we build an admission control webhook for it) we'd like to explicitly mark immutable fields as such, which would require you to explicitly delete-then-recreate. Little bit less declarative at the expense of being a lot less surprising given the constantly reconciling nature of our system.