-
Notifications
You must be signed in to change notification settings - Fork 709
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 is wrong with Helm Chart v0.29.0... #1383
Comments
Please see duplicate issue here #1268 As mentioned, you need to unset default value of
|
/kind support |
Going to close Issue, but please feel free to re-open if the mentioned solution does not work for you. Thanks! /close |
@a7i: Closing this issue. 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/test-infra repository. |
Hi! @a7i Yes, it works when you unset
Also Another question is why to make code updates to master branch but don't create a new release version? /reopen |
Hi @timetofaceit can you please share your policy yaml so I can guide you on setting it up for v1alpha2?
Example:
|
Hi! @a7i Sure! Yes I see that they are available, but I'm getting the same error that I mentioned previously. 😕 My helm chart values file config looks like this now:
|
oh right!
This is not part of release v0.29 and is scheduled for release v0.30 (should be out soon). Please use the README from this release branch: https://github.com/kubernetes-sigs/descheduler/tree/release-1.29 |
Ok, thanks for the info! 👍 Will close this now. |
Hi!
I'm trying to install descheduler using Helm Chart v0.29.0 and set policy profiles in my K8s cluster, but for some reason none of these are working when pods are up... 😢
I see that helm is still installing descheduler with v1alpha1 policy and not accepting v1alpha2. 🤔
Can this be updated / fixed? 🙏
The text was updated successfully, but these errors were encountered: