-
Notifications
You must be signed in to change notification settings - Fork 231
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 local helm releases deletion issue #3243
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more logic is needed
Read local chart name from Chart.yaml update the chart name check lint
56eb937
to
c97cb30
Compare
/approve |
LGTM label has been added. Git tree hash: 46a6bd4fc3a7b0e4b2e772d469c9f1fe95d55271
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kron4eg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/kind bug |
/cherrypick release/v1.8 |
@kron4eg: new pull request created: #3268 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What this PR does / why we need it:
releasesFilterFn
is used to filter out the helm releases that will be uninstalled. When using local helm charts, the helm releases can be deleted without any releases after applyingkubeone apply
again because we are comparing the Chart Name with the path of the Chart (HelmRelease.Chart
is considered a chart path for local usage).This PR will allow kubeone to correctly read the chart name for local and remote helm charts!
Which issue(s) this PR fixes:
Fixes #3211
What type of PR is this?
/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: