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

something wrong with karmada helm chart release artifacts #3912

Closed
chaosi-zju opened this issue Aug 8, 2023 · 1 comment · Fixed by #3931
Closed

something wrong with karmada helm chart release artifacts #3912

chaosi-zju opened this issue Aug 8, 2023 · 1 comment · Fixed by #3931
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Comments

@chaosi-zju
Copy link
Member

What happened:

may be something wrong with our helm chart release artifacts

the image version is inconsistent with release version, just like in karmada-chart-v1.6.2.tgz:

image

What you expected to happen:

the image version of the chart release v1.6.2 should be v1.6.2, ranther than v1.6.0

How to reproduce it (as minimally and precisely as possible):

visit:https://github.com/karmada-io/karmada/releases/tag/v1.6.2
download karmada-chart-v1.6.2.tgz
open the ./karmada/values.yaml
check the image version of karmada-xxx

Anything else we need to know?:

Environment:

  • Karmada version:
  • kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
  • Others:
@RainbowMango
Copy link
Member

/remove-kind bug
/kind cleanup

@karmada-bot karmada-bot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed kind/bug Categorizes issue or PR as related to a bug. labels Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants