App placements rules in Yunikorn contains Provided Rule
, User Name Rule
, Fixed Rule
, Tag Rule
. Every placement example includes a example yaml file and a config yaml file. The sleep pod is described in the example file and the partition is provided in the config yaml file. Before deploying the pods, the configuration field in yunikorn-release/helm/yunikorn/value.yaml should be replaced by the configuration field in the config.yaml.
placementrules: - name: provided create: true parent: name: user create: true
Application submit request by the user developer
, queue in the application on submit: my_special_queue
. Result: root.developer.my_special_queue
placementrules: - name: user create: false # The queue won't be created when the queue doesn't exist.
Application submit request by the user finance.test
, queue does exist: Result: root.finance_dot_test
Application submit request by the user developer
, queue does not exist: Result: failed, next rule executed Solution: The second cases could be submmitted and there are two optional choices.
root.developer
is added to the queues.placementrules: - name: fixed value: last_resort
Application submit request by the user developer
, queue in the application on submit: my_special_queue
. Result: root.last_resort
placementrules: - name: tag value: namespace create: true
Application submit request for a kubernetes based application in the namespace default
by the user developer, queue in the application on submit: my_special_queue
. Result: root.default
Application submit request for a kubernetes based application in the namespace testing
by the user developer
Result: root.testing