Skip to content
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

Open
tico88612 opened this issue Sep 9, 2024 · 9 comments
Open

Upgrade ansible from 9 to 10 (ansible-core from 2.16 to 2.17) #11519

tico88612 opened this issue Sep 9, 2024 · 9 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@tico88612
Copy link
Member

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

@tico88612 tico88612 added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 9, 2024
@tico88612
Copy link
Member Author

tico88612 commented Sep 9, 2024

Unfortunately, if we upgrade ansible-core to 2.17, we cannot support Rocky Linux 8, openSUSE 15.5, RHEL 8, and Amazon Linux 2, which come with Python 3.6 pre-installed. However, the Managed node for ansible-core 2.17 requires Python 3.7 or higher.

ansible/ansible#83357

  • openSUSE 15.5: 31 Dec 2024
  • Amazon Linux 2: 30 Jun 2025
  • RHEL 8: (Maintenance Support) 31 May 2029
  • Rocky Linux 8: (Security EOL) 31 May 2029

@tico88612 tico88612 changed the title Upgrade ansible from 9 to 10 Upgrade ansible from 9 to 10 (ansible-core from 2.16 to 2.17) Oct 9, 2024
@NemesisRE
Copy link

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

@tico88612
Copy link
Member Author

@NemesisRE Do you have a particular reason for updating the max version?

@NemesisRE
Copy link

NemesisRE commented Oct 9, 2024

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?

@tico88612
Copy link
Member Author

I wanted to use an ansible host without the need of an extra venv just for kubespray

Your PR would lead other users to believe this can be used with ansible-core version 2.17. Ansible 9 is based on ansible-core 2.16 and does not specify whether it is compatible with 2.17.

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

if kubespray wants to be compatible with RHEL 8 and Rocky Linux 8 will it use ansible 9 until 2029?

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.

@NemesisRE
Copy link

so realistically we would need a matrix check to make sure the project is future proof

ansible version ansible-core version
9 >=2.16.0 <2.17.0
10 >=2.17.0 <2.18.0
11 >=2.18.0 <2.19.0

@NemesisRE
Copy link

exactly that's what I ment

@tico88612
Copy link
Member Author

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants