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 local helm releases deletion issue #3243

Merged
merged 1 commit into from
Jun 19, 2024

Conversation

mohamed-rafraf
Copy link
Member

@mohamed-rafraf mohamed-rafraf commented Jun 18, 2024

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 applying kubeone 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:

Fix local helm chart releases deletion issue

Documentation:

NONE

@kubermatic-bot kubermatic-bot added docs/none Denotes a PR that doesn't need documentation (changes). release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jun 18, 2024
@mohamed-rafraf
Copy link
Member Author

/assign
/cc @xmudrii @kron4eg

pkg/localhelm/helm3.go Outdated Show resolved Hide resolved
Copy link
Member

@kron4eg kron4eg left a 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

@kubermatic-bot kubermatic-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jun 19, 2024
Read local chart name from Chart.yaml

update the chart name check

lint
@kron4eg
Copy link
Member

kron4eg commented Jun 19, 2024

/approve
/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jun 19, 2024
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 46a6bd4fc3a7b0e4b2e772d469c9f1fe95d55271

@kubermatic-bot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Jun 19, 2024
@mohamed-rafraf
Copy link
Member Author

/kind bug

@kubermatic-bot kubermatic-bot added kind/bug Categorizes issue or PR as related to a bug. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jun 19, 2024
@kubermatic-bot kubermatic-bot merged commit 190dd5a into kubermatic:main Jun 19, 2024
15 checks passed
@kubermatic-bot kubermatic-bot added this to the KubeOne 1.9 milestone Jun 19, 2024
@kron4eg
Copy link
Member

kron4eg commented Jun 26, 2024

/cherrypick release/v1.8

@kubermatic-bot
Copy link
Contributor

@kron4eg: new pull request created: #3268

In response to this:

/cherrypick release/v1.8

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support of installing local fs charts
3 participants