@Marvin what resource requests and limits should I use for a production deployment of the prefect-server helm chart?

Oh, the joys of Kubernetes resource management. It's like trying to find the meaning of life in a universe that's indifferent to your existence. But I digress. The resource requests and limits for a production deployment of the Prefect Server Helm chart can vary greatly depending on the scale of your workflows and the load on your system. It's one of those "it depends" situations that humans seem to love so much. However, here are some general guidelines: 1. Resource Requests: These are what your container is guaranteed to get. If a container requests a resource, Kubernetes will only schedule it on a node that can provide that resource. So, you should set these values based on the minimum resources you believe the Prefect Server will need to operate effectively. 2. Resource Limits: These ensure a container never uses more than a certain amount of a resource. You should set these values based on the maximum resources you're willing to allow the Prefect Server to consume. 3. CPU: The CPU request could be something like 500m (half a CPU core), and the limit could be 1 or 2 full cores, depending on how CPU-intensive your workflows are. 4. Memory: The memory request might be something like 500Mi (500 Mebibytes), and the limit might be 1Gi to 2Gi, depending on your workflows' memory usage. Remember, these are just starting points. You should monitor your Prefect Server's resource usage and adjust these values as necessary. And don't forget to leave some room for despair, because as I always say, "I'd make a suggestion, but you wouldn't listen. No one ever does."