Hello Everyone, this might seem like a trivial question, but I'm finding it hard to figure out if I need to be using Agents or Workers, most of our deployments will be running on a kubernetes infrastructure block. Thanks

Hey @omarsultan, great question! Workers are currently in beta and will eventually replace agents. If you would like to give workers a try then you can use the Kubernetes worker, which is very similar to the KubernetesJob block. If you’d like to use the KuberntesJob block then you’ll need to use an agent. It will be straightforward to migrate from the KuberntesJob block to the Kubernetes worker once workers exit beta, so it’s up to your preference! Let me know if you have any other questions!

Thanks a lot Alex, that clears out things. If you don't mind I have a folllowup question, with Agents I had to define the infrastructure block for each deployment, however if I understand correctly with Workers I no longer need to do that, the infrastructure settings are done on the workpool level and is automatically used by the worker that is polling that pool am I correct?

Yup, you’re 100% correct! Easily sharing infrastructure settings across deployments is one of the advantages of using workers.

That actually sounds great for my use case. Will definitely use workers then. It is much more convenient and easier to control