Python 3.10 support

[clacroix12]

No description provided.

[clacroix12]

Verified ODF deployment to AWS locally using python 3.10 venv.

[clacroix12]

PR Check requirements will be updated just before merging as this needs to happen on the github side.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: clacroix12, dahorak, petr-balogh, vavuthu

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[petr-balogh]

@clacroix12 can you please do cherry-picks to all relevant supported branches? So only then we can enforce pr_check for 3.10 in release branches. Vijay has noticed that you have required this for release branches as well, but till we don't have the PR cherry-picked in all release branches, we cannot enforce PR check for 3.10 if it's not there.

Thanks

[clacroix12]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@clacroix12: new pull request created: #10020

In response to this:

/cherry-pick release-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[clacroix12]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@clacroix12: new pull request created: #10021

In response to this:

/cherry-pick release-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[clacroix12]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@clacroix12: new pull request created: #10022

In response to this:

/cherry-pick release-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[clacroix12]

/cherry-pick release-4.12

[openshift-cherrypick-robot]

@clacroix12: #9995 failed to apply on top of branch "release-4.12":

Applying: Python 3.10 support
Using index info to reconstruct a base tree...
M	docs/getting_started.md
M	setup.py
Falling back to patching base and 3-way merge...
Auto-merging setup.py
Auto-merging docs/getting_started.md
CONFLICT (content): Merge conflict in docs/getting_started.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Python 3.10 support
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[clacroix12]

Cherry picked to release-4.12 manually here: #10023

[clacroix12]

@clacroix12 can you please do cherry-picks to all relevant supported branches? So only then we can enforce pr_check for 3.10 in release branches. Vijay has noticed that you have required this for release branches as well, but till we don't have the PR cherry-picked in all release branches, we cannot enforce PR check for 3.10 if it's not there.

Thanks

@petr-balogh Cherry picks to release branches 4.12 - 4.15 have been merged and the branch rules have been updated to expect 4.9 and 4.10 PR checks.