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

update helm chart to allow complex k8s versions #66

Merged
merged 2 commits into from
Feb 7, 2022

Conversation

jooseppi-luna
Copy link
Collaborator

@jooseppi-luna jooseppi-luna commented Feb 5, 2022

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 the kubeVersion 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:

  • I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
  • I have verified that new and existing unit tests pass locally with my changes
  • I have not allowed coverage numbers to degenerate
  • I have maintained at least 90% code coverage
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • Backward compatibility is not broken

How Has This Been Tested?

Successfully installed the driver with the alternate kubeVersion check on an MKE setup.

@@ -1,6 +1,6 @@
apiVersion: v2
appVersion: "2.1.0"
kubeVersion: ">= 1.21.0 < 1.24.0"
kubeVersion: ">= 1.21.0-0 < 1.24.0-0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

un desired side effect can occur , k8s alpha or beta unstable version will also be supported with this fix
example these k8s versions should be not be supported but this check will allow it
v1.22.0-beta.2
v1.23.1-rc.0

@@ -1,6 +1,9 @@
apiVersion: v2
appVersion: "2.1.0"
kubeVersion: ">= 1.21.0 < 1.24.0"
# If you are using a complex K8s version like "v1.21.3-mirantis-1", use this kubeVersion check instead
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you want to reword complex version to extended version, so they are consistent with the doc changes you are making? Just a suggestion, you can ignore this, not a must change imo.

@jooseppi-luna jooseppi-luna merged commit fec7d4f into main Feb 7, 2022
@jooseppi-luna jooseppi-luna deleted the fix-mirantis-version-issue branch March 16, 2022 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants