I've been trying AX out locally (kind, micro-VM sandbox class) and followed the task example in docs/manifests.md:
spec:
resources:
requests: {cpu: "500m", memory: "1Gi"}
limits: {cpu: "2", memory: "4Gi"}
ax apply succeeds, but the ActorTemplate the controller builds has no resources field - the numbers only appear inside the AX_TASK_YAML env value, so the runner can read them but the actor isn't sized by them. A grep for Spec.Resources across the tree comes back empty. (docs/concepts.md says a Task "declares ... compute requests and limits", and docs/runner.md doesn't mention resources at all, so I'm not sure where these are supposed to be applied.)
Is that intended (the runner applies them itself), or did the wiring get lost?
Happy to share the applied task + the template dump.
I've been trying AX out locally (kind, micro-VM sandbox class) and followed the task example in docs/manifests.md:
spec:
resources:
requests: {cpu: "500m", memory: "1Gi"}
limits: {cpu: "2", memory: "4Gi"}
ax applysucceeds, but the ActorTemplate the controller builds has noresourcesfield - the numbers only appear inside theAX_TASK_YAMLenv value, so the runner can read them but the actor isn't sized by them. A grep forSpec.Resourcesacross the tree comes back empty. (docs/concepts.md says a Task "declares ... compute requests and limits", and docs/runner.md doesn't mention resources at all, so I'm not sure where these are supposed to be applied.)Is that intended (the runner applies them itself), or did the wiring get lost?
Happy to share the applied task + the template dump.