update helm chart to allow complex k8s versions #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The standard kubeVersion check in the Helm chart will fail -- for example, if the k8s version is
v1.21.3-mirantis-1
, the install will abort even if the kubeVersion in the helm chart was specified as>= 1.21.0 < 1.24.0
. Adding a-0
to the end of the version numbers in the kubeVersion field fixes this issue, but it also allows installation of the driver on pre-release alpha and beta versions, which is not supported. Therefore, to make it possible to install the driver on a kubernetes system with an extended version while still blocking pre-release versions of kubernetes, this PR adds a commented-out version of thekubeVersion
check that includes the-0
at the end of the version check and a note explaining it to users.GitHub Issues
dell/csm#128
Checklist:
How Has This Been Tested?
Successfully installed the driver with the alternate
kubeVersion
check on an MKE setup.