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

feature request: private cluster support #506

Open
perezmark opened this issue Oct 1, 2024 · 7 comments
Open

feature request: private cluster support #506

perezmark opened this issue Oct 1, 2024 · 7 comments
Assignees
Labels
area/networking Issues or PRs related to networking kind/feature Categorizes issue or PR as related to a new feature.

Comments

@perezmark
Copy link

Version

Karpenter Version: v0.0.0

Kubernetes Version: v1.30.4

Expected Behavior

Im expecting to auto scale the nodes for testing, i just deployed a simple nginx

Actual Behavior

no nodes provisioned and no events received

Steps to Reproduce the Problem

i just follow the instruction on the documentation page
https://learn.microsoft.com/en-us/azure/aks/node-autoprovision?tabs=azure-cli
except its a private cluster

then deployed 500 replicas of nginx to try to scale, no events happend and stuck on pending because theres in no user ndoes

Resource Specs and Logs

Bash
kubectl create deployment nginx-deployment
--image=nginx:latest
--replicas=3
--dry-run=client -o yaml > nginx-deployment.yaml
Use code with caution.

Then, edit the nginx-deployment.yaml file and add the following nodeSelector under spec.template.spec:

YAML
spec:

... other deployment configurations ...

template:
spec:
# ... other pod configurations ...
nodeSelector:
kubernetes.io/arch: amd64
kubernetes.io/os: linux

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
@Bryce-Soghigian
Copy link
Collaborator

except its a private cluster

Just saw this, IIRC karpenter today does not work with private clusters.

@perezmark
Copy link
Author

except its a private cluster

Just saw this, IIRC karpenter today does not work with private clusters.

What do you mean by IIRC @Bryce-Soghigian

@Bryce-Soghigian
Copy link
Collaborator

"If I recall correctly"

@perezmark
Copy link
Author

perezmark commented Oct 1, 2024

"If I recall correctly"

I tested to provision a public cluster and it worked, any work around with this so that the managed karpenter can reach the a private cluster? @Bryce-Soghigian

@Bryce-Soghigian
Copy link
Collaborator

Bryce-Soghigian commented Oct 2, 2024

I will add seeing whats involved in that work to my todo list before we make the service generally available.

@Bryce-Soghigian Bryce-Soghigian added the area/networking Issues or PRs related to networking label Oct 2, 2024
@tallaxes tallaxes added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 22, 2024
@tallaxes tallaxes changed the title Karpenter not provisioning feature request: private cluster support Oct 22, 2024
@hungvodcm
Copy link

+1 for this, we are also stuck as in our organization we deploy private clusters

@Bryce-Soghigian Bryce-Soghigian self-assigned this Oct 30, 2024
@nfsouzaj
Copy link

nfsouzaj commented Nov 4, 2024

I use private clusters and the node are being provisioned, I am however having problems with the managed identity which I should be opening a ticket soon about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/networking Issues or PRs related to networking kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

5 participants