Upstream ansible(-runner) has always used pip for installs on it's images.
We've kind of ignored this and used packages to add kubernetes and openshift, which hasn't been a problem because everything used the platform python version 3.6.
However, they have moved all their images over to use the python 3.8 module, so this is no longer true.
We need to install the extra libraries using pip or build a pile of dependencies for python 3.8 so they will work with the python 3.8 module rpm.
I do not know if or when this might become a problem downstream. It will depend on whether they continue to use and package everything for the platforms default python or start using modules or other methods to use a newer version of python. As of today the runner image is on RHEL 7 using python 2.7 so upstream and down do not closely resemble each other.
Upstream ansible(-runner) has always used pip for installs on it's images.
We've kind of ignored this and used packages to add kubernetes and openshift, which hasn't been a problem because everything used the platform python version 3.6.
However, they have moved all their images over to use the python 3.8 module, so this is no longer true.
We need to install the extra libraries using pip or build a pile of dependencies for python 3.8 so they will work with the python 3.8 module rpm.
I do not know if or when this might become a problem downstream. It will depend on whether they continue to use and package everything for the platforms default python or start using modules or other methods to use a newer version of python. As of today the runner image is on RHEL 7 using python 2.7 so upstream and down do not closely resemble each other.