You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently working with the AKSNodeClasses CRD, which only includes the properties imageFamily, imageVersion, osDiskSizeGB, and tags. For enhanced functionality, it would be beneficial to add a subnetSelector property.
This addition would enable scaling nodes within specific subnets, a feature not currently supported by AKSNodeClasses. I noticed that EC2NodeClass already supports this through subnetSelectorTerms (as detailed here: Karpenter Documentation). Implementing a similar functionality in AKSNodeClasses could provide more flexibility and control over node deployment in various subnet environments.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
no
Are you currently working around this issue?
no
Additional Context
No response
Attachments
No response
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
The text was updated successfully, but these errors were encountered:
This would allow you to specify a subnet in the AKSNodeClass via the subnets ARM Resource ID. We will not be supporting tags based selection, but you will be able to specify a subnet per nodeclass.
Is this sufficient? Does it solve for your usecase?
Tell us about your request
I am currently working with the AKSNodeClasses CRD, which only includes the properties imageFamily, imageVersion, osDiskSizeGB, and tags. For enhanced functionality, it would be beneficial to add a subnetSelector property.
This addition would enable scaling nodes within specific subnets, a feature not currently supported by AKSNodeClasses. I noticed that EC2NodeClass already supports this through subnetSelectorTerms (as detailed here: Karpenter Documentation). Implementing a similar functionality in AKSNodeClasses could provide more flexibility and control over node deployment in various subnet environments.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
no
Are you currently working around this issue?
no
Additional Context
No response
Attachments
No response
Community Note
The text was updated successfully, but these errors were encountered: