you mean to spin a pod with the agent inside it (daemon in services mode).
Or connect the services queue to the k8s cluster (i.e. define the pod template that uses cpu with not a lot of ram)?
I guess it won’t due to the nature of services?
Correct, k8s glue works differently, that said I would actually use the helm to spin a pod woth the agent in services mode and venv mode.
I want to use services queue for running services, and I want to do it on k8s
So yes, as a standalone pod with the agent in venv mode (as opposed to docker mode)
Does that make sense to you?
I guess the question is - I want to use services queue for running services, and I want to do it on k8s
I guess it won’t due to the nature of services?
Yeah got it. Was mainly wondering if k8s glue was meant for this as well or not