Issue-1417: Improve Dask workers placement on AWS | fixing a minor typo

[limacarvalho]

Fixes | Closes | Resolves #

Please remove anything marked as optional that you don't need to fill in.
Choose one of the keywords preceding to refer to the issue this PR solves, followed by the issue number (e.g Fixes # 666).
If there is no issue, remove the line. Remove this note after reading.

Changes introduced in this PR:

• Fixes related to [BUG] - Unable to force Dask workers to run on AWS EKS specific nodegroups  #1417
• A minor typo correction

Types of changes

What types of changes does your PR introduce?

Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests?

• Yes
• No

Documentation

Does your contribution include breaking changes or deprecations?
If so have you updated the documentation?

• Yes, docstrings
• Yes, main documentation
• Yes, deprecation notices

Further comments (optional)

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.

[iameskild]

Hey @limacarvalho! Thank you for your contribution :)

Some of the CI tests will fail because this PR is coming from a fork (an issue we are aware of) however would you mind running pre-commit on these files?

[alimanfoo]

Hi there, just chiming in to say I'm also hitting the same issue with nebary 2022.10.1 on GCP not being able to place worker and scheduler pods into specific node groups, and would love to see this fix get merged! Kudos @limacarvalho for bottoming this one out 🙏

[iameskild]

@limacarvalho @alimanfoo I apologize for the delay! We very much appreciate this bug fix and will make sure we get around to reviewing and merging this incoming PRs more quickly next time around! :)