I am confused by this. The UX of the CLI is almost identical to kubectl, but it doesn't seem to actually be built on K8s CRDs. There's a backend that runs on k8s, but doesn't seem natively integrated.
Because it's using `ax apple` instead of `kubectl apply` you can't use tools like argocd for managing resources.
It's built on agent substrate which is built on top of k8s CRDs, so I'm surprised.
Is the throughput of these objects too high for etcd?
zactato · · focus · HN ↗
Because it's using `ax apple` instead of `kubectl apply` you can't use tools like argocd for managing resources.
It's built on agent substrate which is built on top of k8s CRDs, so I'm surprised.
Is the throughput of these objects too high for etcd?
ahmedtd · · focus · HN ↗
Yes (perhaps not etcd, but the combination of kube-apiserver and etcd)
Substrate does not use CRDs for anything on the hot path of actor scheduling or resumption.