kopf VS fastapi-crudrouter

If you're looking for more examples beyond what was shown and referenced above, I recommend exploring other popular tools that make use Python Kubernetes client, such kopf - the library for creating Kubernetes operators. I also find it very useful to take a look at tests of the library itself, as it showcases its intended usage such this client test suite.

Depending on how you want to configure your selecting logic, it can be solved by mutating admission webhooks for the pods. For example, in Kopf, the simplest approach would be:

Hello. Kopf (a framework to write Kubernetes operators in Python) 1.31 is released and has finally got admission webhooks — https://github.com/nolar/kopf/releases/tag/1.31.0. I would appreciate some feedback from experienced operator developers on how easy or hard it is to write webhooks now, and what is missing and makes it inconvenient. The docs: https://kopf.readthedocs.io/en/stable/admission/ For a brief preview, it looks like this:

Correct, using generic resources with Client.watch should work. In general to create more complex operators I would recommend to check out kopf.

FastAPI does have an equivalent. Something like this? https://github.com/awtkns/fastapi-crudrouter

I can't show any pics cuz of uk NDA and all that. I can tell you the gist of it though. FastAPI is already pretty good at the abstraction part. Our middleware had a lot of rerouting and it was basically just a bunch of redundant functions. I just used this cool ass package https://fastapi-crudrouter.awtkns.com/ and used the partial function from functools to generate endpoints for every scenario/db tables.

Thanks, that's a really helpful example.

Where I think this could be taken to the next level of reusability is in modularising the front-end into API-specific components. For example, the login behaviour could depend on FastAPI-Users, with a sibling frontend library containing components that implement the same login flow. Adding user behaviour is then a matter of using the same third-party library on the front and back end.

This approach could be extended to other components such as an admin panel (perhaps using https://github.com/awtkns/fastapi-crudrouter), or a blogging component.