negz

6 ms·

1.
by negz 3mo ago
I'm the post author, and a long-time Crossplane maintainer. To my knowledge this is the most advanced open source control plane anyone's built with Crossplane. Happy to chat about what worked well and what didn't building thi
2.
I built a fleet-scale inference control plane using Crossplane(blog.crossplane.io)
2 points by negz 3mo ago|1 comments
3.
by negz 4y ago
Why not both? ;) - https://github.com/crossplane-contrib/provider-terraform
4.
by negz 4y ago
We certainly design Crossplane with the intent that end-users will interact with a "Composite Resource" API, not use MRs directly. Little bit like end-users using a Terraform module curated by their platform team rather than writi
5.
by negz 4y ago
We'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
6.
by negz 4y ago
Haha I noticed that also shortly after I made this graphic. I've used it in a few talks and posts now and always worried someone would notice. Good eye.
7.
by negz 4y ago
Correct. We take the control plane of Kubernetes and extend it so that it can be used to configure/orchestrate anything, not just containers.
8.
by negz 4y ago
Post author here - thanks for the kind words! I wouldn't say Crossplane is _supposed_ to be used together with CD systems (that's optional) but that's certainly a common and practical use case.
9.
by negz 6y ago
I wasn't familiar with Atlantis - thanks for the pointer!
10.
by negz 6y ago
OP here - this is enabled by a mix of tooling consistency (e.g. everything can happen in the same Kubernetes API server) and carefully designing our "managed resources" - the custom resources that represent bits of infra - to be a
11.
by negz 10y ago
I believe we expect moving to the cloud to be more expensive than running our own DCs as you suggest, but I don't believe that takes into account any 'wasted developer time' you might factor into this. I believe we started bu
12.
by negz 10y ago
It's strange (or perhaps rather unfortunate) to me as an SRE at Spotify as well. Helios is in many ways similar to Kube, so it was our hope that eventually it would lead us to scheduling multiple service containers per physical machine
13.
by negz 10y ago
FWIW a team of largely men using womens' names for servers always felt a bit icky to me personally for reasons I couldn't quite enunciate. We now use ungendered serial numbers.
14.
by negz 10y ago
Post author here. A bunch of stuff was glossed over as the post was more focused on the stack's history and evolution than specific technical details. Ideally we hope to provide some followup posts that go deeper into technical detail