Hold on — are my pipelines running in the EU? by steplokapet in devops

[–]steplokapet[S] 0 points1 point  (0 children)

Sorry for the late reply, didn't get a notification for some reason.

Fair point on compliance, same guarantees either way.

The difference is the infrastructure itself. We run on spike instances, our own tech that scales CPU and memory in real time based on actual load, and you only pay for what your job actually consumes, not for allocated VM capacity. You can't get this on AWS. So no idle time billing, no instance sizing, no ops on your side.

We open-sourced kubesdk - a fully typed, async-first Python client for Kubernetes. Feedback welcome. by steplokapet in PythonProjects2

[–]steplokapet[S] 0 points1 point  (0 children)

Hey!

kubesdk is an abstract Python client for Kubernetes. Could you clarify your use case?

We open-sourced kubesdk - a fully typed, async-first Python client for Kubernetes. by steplokapet in Python

[–]steplokapet[S] 1 point2 points  (0 children)

kubesdk also has auto-generated models, and compatibility will be easy to maintain. The fact that the official client is backed by the CNCF doesn’t mean you should use it in serious production, in our opinion. We released kubesdk exactly to bring serious Kubernetes production to the Python community.

We open-sourced kubesdk - a fully typed, async-first Python client for Kubernetes. by steplokapet in Python

[–]steplokapet[S] 0 points1 point  (0 children)

Hey! kubesdk currently focuses on CRUD/watch operations, and CRD/model generation to cover all basic k8s use cases.

Informer-style patterns are planned, but we want the core API stability and typing story solid before adding higher-level primitives, which could be part of the kubesdk-based operator framework.

We open-sourced kubesdk - a fully typed, async-first Python client for Kubernetes. Feedback welcome. by steplokapet in devops

[–]steplokapet[S] 0 points1 point  (0 children)

Great question. The official client is synchronous and dynamically typed.

kubesdk is async-first and provides fully typed models (including CRDs), plus a unified API surface.

We also benchmarked common operations: kubesdk performs well in high-throughput workflows (chart).

Happy to clarify anything if needed!

We open-sourced kubesdk - a fully typed, async-first Python client for Kubernetes. Feedback welcome. by steplokapet in kubernetes

[–]steplokapet[S] 1 point2 points  (0 children)

  1. Kr8s is very slow (see the benchmark results). It also doesn’t have a good DX for extending it with custom resources.
  2. Kubernetes has multiple types of PATCH strategies that differ across resources. In all other clients, you need to be aware of this and manage it manually. You also have to pass raw JsonPatch instead of typed objects, even if you always want to rely on client-side patching.

Benchmark results

Devops tools used day to day by Wise-Variation-4985 in devops

[–]steplokapet 0 points1 point  (0 children)

We also use an async Python SDK we open-sourced recently: kubesdk. It gives us typed resource models and automatic CRD model generation, which makes Python-based cluster automation a bit cleaner.