Fix "matchExpressions" for "nodeAffinity"

[chs2]

No description provided.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[amoghrajesh]

@chs2 can you please update the PR description? Its hard to tell what you are trying to achieve without a description

[hussein-awala]

matchExpressions should be an array of expressions, LGTM

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

[amoghrajesh]

@chs2 are you working on this actively? Requires small nit handling and a rebase (doing it)

[amoghrajesh]

Reopened to run the latest set of CI on the PR

[chs2]

@chs2 are you working on this actively? Requires small nit handling and a rebase (doing it)

To be true, no I'm not.
I wouldn't have thought it would raise so many questions.
While working on a airflow1-to-airflow2 migration I found the Airflow1 KubernetesPodOperator documentation. I noticed the typo and thought it would be nice to have it fixed for anyone in the same situation.

[eladkal]

Ah wait
This PR is targeted the v-10-stable branch. This is why it was confusing.
We are not having any more releases for Airflow 1.10

[potiuk]

Ah yes.