Daniel Grenemark
Daniel Grenemark
@CecileRobertMichon long shot here.. but the underlying Azure resources for AzureMachines are not immutable which I would consider a high risk of having the Azure resource in a non-functional state...
MHC support would get the job done!
As a workaround I configured the output with `tls.verify Off`. Not optimal, but it gets the job done for now.
I just ran into this myself when running multiple `MachinePools`. I did some debugging and noticed that the `normalizedProviderID` translates to the VMSS instance number (0, 1, 2, 3, 4,...
I'd say normalizing the provider id is the issue here since it's CA a specific behaviour and it should normalize to something that works independent of the provider (or refactor...
> I guess we should also include resource group name and subscription-id to guarantee ID uniqueness and avoid other potential conflicts? I agree with this. But rather than extracting the...
> Thanks for the feedback. This couldn't be supported with current LoadBalancer sku as lots of resources are shared, but it is under the plan with container native LoadBalancer (which...
> @desek can you open this very same issue also at https://github.com/Azure/AKS/issues > > The AKS Product Group monitors that repo and might consider your issue for their [roadmap](https://github.com/Azure/AKS/projects/1) >...
May is coming fast. Any updates to planned release date?
I noticed there hasn't been any new Windows Server 2022 images published since `130.3.20240717`. Any updates when we should expect new images to be published?