Closed Ebaneck closed 4 years ago
For me we need our custom module/utils to handle both version of python-kubernetes
for the moment 8.0 and 10.0.
In the futur with #2029 I think we will need our salt module/utils to be compatible with at least one version before
Maybe it's a case where we need to upgrade the client before attempting to use it? It would make sense to have "the good version" in our Salt master
Or we can upgrade bootstrap stuff before doing anything else (meaning we upgrade bootstrap before patching the namespace version and running the upgrade pre-check states)
Component:
'kubernetes', 'salt'
What happened:
A typical user is unable to upgrade between MetalK8s patch versions
What was expected:
I should be capable of upgrading from one patch version to another. In my case from MetalK8s 2.4.1 to 2.4.2
Steps to reproduce
Resolution proposal (optional): TBD