-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade ansible from 9 to 10 (ansible-core
from 2.16 to 2.17)
#11519
Comments
Unfortunately, if we upgrade
|
ansible-core
from 2.16 to 2.17)
Would it not be possible to allow 2.17.x as max version and still use 2.16 for the tests of those OS's |
@NemesisRE Do you have a particular reason for updating the max version? |
I wanted to use an ansible host without the need of an extra venv just for kubespray if kubespray wants to be compatible with RHEL 8 and Rocky Linux 8 will it use ansible 9 until 2029? |
Your PR would lead other users to believe this can be used with Creating Virtualenv is the recommended method, as it does not interfere with the original system's default version of Python. FYI: https://kubespray.io/#/docs/ansible/ansible
With the current information, unfortunately, Yes. Unless there comes a time when we think it will be more difficult to maintain (10 years is not a short time), we will consider removing support for systems that come with Python 3.6 pre-installed. |
so realistically we would need a matrix check to make sure the project is future proof
|
exactly that's what I ment |
/lifecycle frozen |
What would you like to be added
We would need to manually upgrade ansible to 10 (ansible-core 2.17).
Why is this needed
Our CI would fail the
playbooks/ansible_version.yml
check and ansible 9 will deprecated at Nov. 2024.PR #11462
FYI: https://endoflife.date/ansible
The text was updated successfully, but these errors were encountered: