Open szczeles opened 1 year ago
Pipeline generator sanitizes the node name to be kubeflow-compatible, but when it comes to details selection (like resources, tolerations), it doesn't follow the same logic, it purely checks for op name: https://github.com/getindata/kedro-kubeflow/blob/0.7.4/kedro_kubeflow/generators/utils.py#L177
Therefore, with the Kedro node named some_node, and specific resources for some_node, it uses defaults instead. We should check for uncleaned name in the config file to cover cases like this.
some_node
Pipeline generator sanitizes the node name to be kubeflow-compatible, but when it comes to details selection (like resources, tolerations), it doesn't follow the same logic, it purely checks for op name: https://github.com/getindata/kedro-kubeflow/blob/0.7.4/kedro_kubeflow/generators/utils.py#L177
Therefore, with the Kedro node named
some_node
, and specific resources forsome_node
, it uses defaults instead. We should check for uncleaned name in the config file to cover cases like this.