This repository has been archived by the owner on Feb 2, 2024. It is now read-only.
chore: set required kubeVersion because of Ingress resource #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tumido
force-pushed
the
add-kubeversion-requirement
branch
from
bb4b9bb
to
60b5729
Compare
Signed-off-by: Tomas Coufal <tcoufal@redhat.com>
tumido
force-pushed
the
add-kubeversion-requirement
branch
from
60b5729
to
279dfbe
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 of the change
The latest kubernetes version restriction I've found is that the upstream chart uses
Ingressresource which went GA in1.19.0.Existing or Associated Issue(s)
N/A
Additional Information
Checklist
Chart.yamlaccording to semver.values.yamland added to the README.md. The helm-docs utility can be used to generate the necessary content. Usehelm-docs --dry-runto preview the content.ct lintcommand.