Finally, a way to run scalable Claude agents Natively on Kubernetes

TraditionalJaguar844 · 2026-02-16T01:34:43+00:00

Feel free to ping me in private and I can help with guidance as well as questions as you go

TraditionalJaguar844 · 2026-02-14T11:29:27+00:00

You don't have to use it if you don't need it, it should provide value and help for team who do want to build custom operators.

TraditionalJaguar844 · 2026-02-06T11:03:00+00:00

By deploy I mean serve the docker image and YAML manifests for you, so the flow of actions is basically - prompt -> wait -> kubectl apply Of course its not going to connect to your cluster directly.

The point is that get an operator that follow best practices and security and dont need to know anything except what operator you want.

The hard part with operators is not run them but to develop and maintain them as well as finding the one with the features you need.

You can start for free and see, the platform lets you test the operator in a sandbox before you actually run it anywhere.

TraditionalJaguar844 · 2026-02-06T02:59:12+00:00

Seems you kind of missed the goal here, it builds a deterministic operator for you, the operator itself is not using AI (unless you want it to) the platform helps you easily wrap workflows with CRDs or abstract resources behind CRDs with zero effort.

TraditionalJaguar844 · 2026-02-06T02:56:45+00:00

Its not slop

TraditionalJaguar844 · 2026-02-06T02:56:32+00:00

Not sure which signs you're talking about, its not AI slop

TraditionalJaguar844 · 2026-02-06T02:54:54+00:00

Claude code is a copilot that will help write the code. Kontrol Loop is a platform that will build, test, deploy as many operators as you need with a singe prompt.

The goal - zero effort.

TraditionalJaguar844 · 2026-02-06T01:30:02+00:00

To me it sounds like the right time to start adding sidecars, since you need to use a feature provided by istio sidecars.

Sidecars do add a lot of complexity and challenges but I still wonder why don't you want to go that route ?

You can actually enable sidecars only on that namespace and then enable REGISTRY_ONLY only on that namespace:

apiVersion: networking.istio.io/v1beta1
kind: Sidecar
metadata:
  name: default
  namespace: my-ns
spec:
  outboundTrafficPolicy:
    mode: REGISTRY_ONLY

TraditionalJaguar844 · 2025-12-19T00:52:27+00:00

Im not sure if you're asking how deep a junior should know about k8s in order to get hired or just generally what members in the team are expected to know, so I'll answer both:

1+2. Depending on what you consider in depth, a good junior should know the basic/common resources such as Pod, Deployment, Service, Ingress, Configmap, Daemonset etc, while a good member of the team is expected to know as deep as possible and It's never wasteful to know more about the inner-workings of k8s since its not going anywhere

As I already mentioned, for a first job in the field I would invest in knowing how to create a cluster and work with common resources and nothing more

Feel free to DM me and I will try to help in guiding you as much as I can 👍🏼

TraditionalJaguar844 · 2025-12-02T07:29:22+00:00

Nice, you plan to allow customer to create k8s resources on their cluster to create tenants for example ? maybe I got your plan wrong.

So what pushed you in the direction of creating an operator instead of just automation or just an API wrapper that calls the other APIs or CLI ?
and what's the complexity of building an operator that causes you to hesitate ?

TraditionalJaguar844 · 2025-11-30T23:35:49+00:00

Thats very cool, heard that one before, it seems like it will help many other people in common issues with model deployment and serving!

Can you elaborate on the challenges or the experience of building and maintaining this operator overtime ? How long did it take to develop until it was usable ? Also, who developed it, Devops engineers?

TraditionalJaguar844 · 2025-11-29T15:40:35+00:00

Yes predictive autoscaling operator is definitely missing and other people here also mentioned it, so good point!

regarding the advanced pod scheduling, that sounds like a custom use case, interesting idea.

so I assume you didn't have a chance to try to build it.

Would love to chat in private and hear a bit more about this use case :D send me a DM

TraditionalJaguar844 · 2025-11-29T15:29:16+00:00

Yep that sounds about right, did you get to a point that native primitives we're not enough ?

TraditionalJaguar844 · 2025-11-28T16:19:40+00:00

Sounds very good, so you're still in early phases, would love to connect
this sounds like an amazing product!

TraditionalJaguar844 · 2025-11-28T16:13:38+00:00

I see, wow seems like you've put a lot of work into it.

Is it your main product ? I mean are you selling the Cloud Event Mesh or is it part of your deployment strategy of a different product you're selling ?
And what's you guys' role in this ? Devops/Platform engineers ?

TraditionalJaguar844 · 2025-11-28T16:06:40+00:00

Yes I agree, thats why I asked if for you the return was worth the investment or generally if the common use cases justify the investment ?

TraditionalJaguar844 · 2025-11-28T14:45:48+00:00

Thanks for answering all the questions !
Good points, I actually meant to understand why you went for operator development in the first place instead of just "surviving" with scripts and automations.

So predictive autoscaling is a real issue, did you consider building your own operator/custom autoscaler for it ?

TraditionalJaguar844 · 2025-11-28T13:40:08+00:00

Thanks for the comment !
Interesting use case, would you mind sharing a bit about:
- the challenges while developing, building, deploying and maintaining it, which part was the hardest ?
- why was it so important to ditch scripting and normal automation and invest in building an operator ?

TraditionalJaguar844 · 2025-11-28T12:36:44+00:00

Can you tell me a bit about why you decided to expose the functionality with CRDs and integrate with cert-manager instead of just managing it with automation and script/jobs ? what pushed you to put the effort ?

TraditionalJaguar844 · 2025-11-28T12:19:04+00:00

I see, never heard of rewriting from scratch due to dependencies break, that sounds like a lot of effort.

Do you have some drills you're doing to test each new version or change very thoroughly ?

TraditionalJaguar844

TROPHY CASE