-
Notifications
You must be signed in to change notification settings - Fork 964
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
Fail to upgrade from 0.32.3 to 0.33.0 #5366
Comments
|
Pod crash on start
|
@mikkoc I think you noticed this, but the cluster-name is missing. That happened to me. In the upgrade notes, the Helm chart values paths changed (which is a breaking change...) Your chart uses Double check the release notes, but you should just need to update your TF code to replace all |
Helm command from the documentation:
Note these values: And note your values:
|
You're right, I must have missed this. It works now, thanks @jls-appfire I will close this issue. |
@jls-appfire would it be possible to add a warning in the upgrade guide for 0.33 here https://karpenter.sh/docs/upgrading/upgrade-guide/#upgrading-to-v0330? This is a breaking change that's not documented in the upgrade guide. |
The helm chart value migration is part of the v1beta1 migration guide. |
@mikkoc @sde-melo Can you share the actual deployment output with
kubectl get deploy -n $KARPENTER_NAMESPACE karpenter
. That should help us see the environment variables that are being used here so we can see if the problem is at the binary level or if it is at the helm level.Originally posted by @jonathan-innis in #5340 (comment)
We use Terraform to manage this and the
karpenter-crd
Helm ChartThe text was updated successfully, but these errors were encountered: