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

conversion webhook and non default namespace #607

Open
gitarns opened this issue Dec 4, 2024 · 2 comments
Open

conversion webhook and non default namespace #607

gitarns opened this issue Dec 4, 2024 · 2 comments

Comments

@gitarns
Copy link

gitarns commented Dec 4, 2024

Version

Hello,

v0.7.0

After installing Karpenter in any non-default (kube-system) namespace , installing NodePool and AKSNodeClass (as per the documention) will fail with:

conversion webhook for karpenter.sh/v1beta1, Kind=NodePool failed: Post "https://karpenter.kube-system.svc:8443/conversion/karpenter.sh?timeout=30s": service "karpenter" not found

Karpenter service is hard-coded to the kube-system namespace.

Expected Behavior

Karpenter works in non-default NS.

Actual Behavior

Convertion webhook doesn't work.

Steps to Reproduce the Problem

Install Karpenter in non-default NS.

Resource Specs and Logs

conversion webhook for karpenter.sh/v1beta1, Kind=NodePool failed: Post "https://karpenter.kube-system.svc:8443/conversion/karpenter.sh?timeout=30s": service "karpenter" not found

Community Note

  • 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
@brunosimsenhor
Copy link

It seems the CRDs are hard-coding the service namespace to kube-system for conversion webhooks.

@philchristensen
Copy link

philchristensen commented Jan 8, 2025

This also prevents users from running Karpenter in AWS Fargate, because you can't run the entire kube-system NS in Fargate.

I'm starting to doubt the value of this particular use-case, but still...

edit: sorry, didn't realize this was the Azure provider.

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

3 participants