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

Failed to watch *v1.NodeClaim: failed to list *v1.NodeClaim: request to convert CR from an invalid group/version: karpenter.sh/v1beta1 #1886

Open
saikumarbommakanti opened this issue Dec 17, 2024 · 11 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@saikumarbommakanti
Copy link

Description

Observed Behavior:
Failed to watch *v1.NodeClaim: failed to list *v1.NodeClaim: request to convert CR from an invalid group/version: karpenter.sh/v1beta1
Expected Behavior:
the karpenter helm chart was upgraded to v1.1.0 but seeing the above error
Reproduction Steps (Please include YAML):
Install the karpenter v1.1.0 on eks cluster and was not able to bring the kapenter pod up
Versions:

  • Chart Version: v1.1.1
  • Kubernetes Version (kubectl version): v1.31.2 is the server version
  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@saikumarbommakanti saikumarbommakanti added the kind/bug Categorizes issue or PR as related to a bug. label Dec 17, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 17, 2024
@jmdeal
Copy link
Member

jmdeal commented Dec 17, 2024

Did you ensure all stored versions of Karpenter's CRs were migrated to v1 before upgrading to v1.1.0? There's a reference to how to validate this in the upgrade guide.

/triage needs-information

@k8s-ci-robot k8s-ci-robot added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 17, 2024
@saikumarbommakanti
Copy link
Author

saikumarbommakanti commented Dec 18, 2024

Yes it was migrated to v1.1.0, but the error says failed to list *v1.NodeClaim: request to convert CR from an invalid group/version: karpenter.sh/v1beta1
for crd in "nodepools.karpenter.sh" "nodeclaims.karpenter.sh" "ec2nodeclasses.karpenter.k8s.aws"; do

kubectl get crd ${crd} -ojsonpath="{.status.storedVersions}{'\n'}"

done

["v1"]

["v1"]

["v1"]

@jmdeal
Copy link
Member

jmdeal commented Dec 19, 2024

What version of Karpenter did you migrate from to v1.1.0 and did you check this before performing the upgrade?

@saikumarbommakanti
Copy link
Author

it was from 0.36.0 to v1.1.0

@jmdeal
Copy link
Member

jmdeal commented Dec 19, 2024

Did you upgrade directly, or did you upgrade through v1.0?

@abhilashsupare
Copy link

I am also facing the same issue, I have upgraded from v1.0.0 to v1.1.0,

@jmdeal
Copy link
Member

jmdeal commented Dec 19, 2024

@abhilashsupare did you follow all of the steps in the migration guide, particularly ensuring that all stored versions for CRs were migrated before upgrading?

@saikumarbommakanti
Copy link
Author

Yes it was migrated to v1.1.0, but the error says failed to list *v1.NodeClaim: request to convert CR from an invalid group/version: karpenter.sh/v1beta1
for crd in "nodepools.karpenter.sh" "nodeclaims.karpenter.sh" "ec2nodeclasses.karpenter.k8s.aws"; do

kubectl get crd ${crd} -ojsonpath="{.status.storedVersions}{'\n'}"
done

["v1"]

["v1"]

["v1"]

@saikumarbommakanti
Copy link
Author

yes it is migraded and pasted you the output

@jmdeal
Copy link
Member

jmdeal commented Dec 20, 2024

@saikumarbommakanti I'm trying to understand what steps you took to migrate from v0.36.0 to v1.1.0. Did you upgrade directly, or did you upgrade to v1.0.x as an interim step. If you did, what patch version of v1.0.x did you migrate to? Did you follow the steps in the migration guide, and if not could you explain what steps you took?

@jmdeal
Copy link
Member

jmdeal commented Dec 23, 2024

/assign jmdeal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants