3 ms·
Since Go got generics, working with the Kubernetes API could become far more ergonomic. It's been pulling teeth until now. I'm eager to see how the upstream API
by jzelinskie 4y ago
Since Go got generics, working with the Kubernetes API could become far more ergonomic. It's been pulling teeth until now. I'm eager to see how the upstream APIs change over time.
In the mean time, one of the creators of the Operator Framework[0] built a bunch of useful patterns using generics that we used to build the SpiceDB Operator[1] called controller-idioms[2].
Does anyone know of other efforts to improve the status quo?
[0]: https://operatorframework.io https://operatorframework.io
[1]: https://github.com/authzed/spicedb-operator https://github.com/authzed/spicedb-operator
[2]: https://github.com/authzed/controller-idioms https://github.com/authzed/controller-idioms
- aliasxneo 4y agoThis was part of why I chose Python with the last operator I wrote. Granted, it was a slow process that wasn't time-sensitive (and couldn't be paralleled), so performance wasn't a concern. Regardless, I avoided Go because of previous experiences with how hard a lack of generics made working with such things. I'm hoping things are improving. Maybe I'll consider it for the next one I write.