-
Notifications
You must be signed in to change notification settings - Fork 74
Issues: Azure/karpenter-provider-azure
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Transient failure in unit test: "valid format with mixed-case resource group and subnet name"
#743
opened Mar 21, 2025 by
charliedmcb
Does self-hosted karpenter have the same limitation/unsupported features as NAP
#741
opened Mar 19, 2025 by
vincent-zouzou
Some zonal regions (like eastus2euap) are treated as non-zonal
area/availability-zones
Issues or PRs related to availability zones
kind/bug
Categorizes issue or PR as related to a bug.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#731
opened Mar 11, 2025 by
tallaxes
how to allow karpenter to only use sku with ephemeral OS disk support ?
#683
opened Feb 7, 2025 by
flbla
Workloads that rely on workload identity don’t function on nodes created by Karpenter
#563
opened Nov 4, 2024 by
nfsouzaj
Load balancing doesn't work correctly in BYO VNET scenarios
area/networking
Issues or PRs related to networking
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#562
opened Nov 4, 2024 by
ohorvath
Spot instances ephemeral disk size limit is not taken into consideration
area/spot
Issues or PRs related to spot
area/storage
Issues or PRs related to storage
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
#518
opened Oct 12, 2024 by
krukowskid
Installation scripts all assume default azure CLI output format of JSON
#515
opened Oct 9, 2024 by
swgriffith
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.