HomeSoftware Heritage

loaders: Fix affinity configuration

Description

loaders: Fix affinity configuration

Currently, the scheduling refuses to go through with the error message:

0/4 nodes are available: 4 node(s) didn't match Pod's node affinity/selector.

Details

Provenance
ardumontAuthored on Aug 26 2022, 10:11 AM
ardumontPushed on Aug 26 2022, 10:13 AM
Parents
R260:97f1d07db95e: loaders: Update default values with examples
Branches
Unknown
Tags
Unknown
Reverted By
R260:59b027d5b7a0: Revert "loaders: Fix affinity configuration"