Allow resource overcommitting when running functions in Kubernetes #4829
Conversation
|
rerun cpp tests |
1 similar comment
|
rerun cpp tests |
|
@sijie currently we don't have any validation logic for any function worker configs. We definitely should add that validation logic. Preferably using the annotation based validation framework I introduced before. Lets create an issue for this to add validation framework for worker configs, since currently there is nothing of there. For this PR, lets not add a one off check just for that config. |
|
I don't think there is validation for any of the broker config as well :/ |
Please create the issue and link it here and add a TODO item with the link to the newly added fields. So we don't forget about it. |
…pache#4829) Currently, when running Pulsar Functions, Sources, and Sinks in Kubernetes. The resources requests and resource limits are set to the same values. While this is ok and everything will run as it should, actual resource utilization in the cluster might be low. To increase actual resource utilization, we need to be able to overcommit a certain amount in our clusters
Motivation
Currently, when running Pulsar Functions, Sources, and Sinks in Kubernetes. The resources requests and resource limits are set to the same values. While this is ok and everything will run as it should, actual resource utilization in the cluster might be low. To increase actual resource utilization, we need to be able to overcommit a certain amount in our clusters