Tagged api-compatibility
2 write-ups.
Choosing an Unreleased API Over the One Already There
I removed a dependency on an unreleased router method in two lines and watched it pass CI on three Node versions, then put it back, because a public method is better code than the private field I had swapped in. I priced that choice at a few weeks and never priced it again.
Reimplementing Enough of Kubernetes to Fool kubectl
Reimplementing enough of the Kubernetes API that the real kubectl can't tell the difference. The surprise wasn't the resource schemas; it was that kubectl delegates its own output formatting to the server, and that a Quantity sent as a plain string decodes as zero on the client rather than erroring.