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

bug: tool fails with Karpenter v1.0 and new APIs #315

Open
mbevc1 opened this issue Aug 23, 2024 · 3 comments
Open

bug: tool fails with Karpenter v1.0 and new APIs #315

mbevc1 opened this issue Aug 23, 2024 · 3 comments

Comments

@mbevc1
Copy link
Contributor

mbevc1 commented Aug 23, 2024

Using latest Karpenter v1.0.1, the toll fails with:

0823 16:41:56.172646  107653 reflector.go:535] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:229: failed to list *v1beta1.NodeClaim: conversion webhook for karpenter.sh/v1, Kind=NodeClaim failed: Post "https://karpenter.kube-system.svc:8443/conversion/karpenter.sh?timeout=30s": service "karpenter" not found
E0823 16:41:56.172703  107653 reflector.go:147] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:229: Failed to watch *v1beta1.NodeClaim: failed to list *v1beta1.NodeClaim: conversion webhook for karpenter.sh/v1, Kind=NodeClaim failed: Post "https://karpenter.kube-system.svc:8443/conversion/karpenter.sh?timeout=30s": service "karpenter" not found

We probably need to bump deps and APIs?

@punkwalker
Copy link
Contributor

punkwalker commented Sep 13, 2024

There are two parts to this issue.

First, eks-node-viewer still uses v1Beta1 Karpenter APIs, which should be fixed with #316.

Second, The v1 CRDs include a conversion webhook to convert resources from v1Beta1 to v1.
It has to be in the same namespace as Karpenter deployment. Until the PR is merged there are two solutions:

  1. Make sure the CRDs are installed/upgraded as per step 5 in instructions here
  2. Manually update v1beta1 resources to v1 and only use v1 resources.

@mbevc1
Copy link
Contributor Author

mbevc1 commented Sep 13, 2024

To link you PR #316 bumping to v1 😉

@mbevc1
Copy link
Contributor Author

mbevc1 commented Sep 13, 2024

It was linked to #315 not #316 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants