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

Fix installation of ingressclass resource via helm chart on certain kubernetes versions #1228

Merged
merged 1 commit into from
Nov 17, 2020

Conversation

Dean-Coakley
Copy link
Contributor

Bug

Helm will fail to install the ingressclass resource when the patch value of the semver contains some non-numerical suffix.

For example:

  • v1.18.8-rc.1
  • v1.18.10-gke.601

Proposed changes

On kubernetes versions v1.18.*-*(see examples above) the ingressclass resource is installed successfully:

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING doc
  • I have checked that all unit tests pass after adding my changes
  • I have updated necessary documentation
  • I have rebased my branch onto master
  • I will ensure my PR is targeting the master branch and pulling from my branch from my own fork

Bug first appeared in: d893dd0

Helm will fail to install the ingressclass resource when the patch value
of the semver contains some non-numerical suffix.

For example:
* v1.18.8-rc.1
* v1.18.10-gke.601
@Dean-Coakley Dean-Coakley added the bug An issue reporting a potential bug label Nov 16, 2020
@Dean-Coakley Dean-Coakley self-assigned this Nov 16, 2020
Copy link
Contributor

@pleshakov pleshakov left a comment

Choose a reason for hiding this comment

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

👍

@Dean-Coakley Dean-Coakley merged commit 69f55aa into master Nov 17, 2020
@Dean-Coakley Dean-Coakley deleted the fix-ingressclass-semver-check branch November 17, 2020 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue reporting a potential bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants