Anonymous

My feedback

  1. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous commented  · 

    happened to take a look at this issue, currently 4 tags will be created for azure disk PVC:

    3 tags are here:
    https://github.com/kubernetes/kubernetes/blob/e8bf254db8b1cb8048849d3a74d336567ac35fe7/pkg/controller/volume/persistentvolume/pv_controller.go#L1438-L1440
    1 specific tag is here:
    https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/azure/azure_managedDiskController.go#L83-L84
    One way is add a tags parameter in azure disk storage class, and then when dynamic provision an azure disk, user defined tags will be created in azure disk creation time. Not sure this could be the disired requirement?

  2. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Anonymous commented  · 

    This issue has been resolved in k8s v1.12.0 by feature: Enable dynamic azure disk volume limits:
    https://github.com/kubernetes/kubernetes/pull/67772
    Before v1.12.0, the maximum disk number of node is always set as 16 by default, so if it’s a little VM size that only supports 8 disk attachment, there would be error after attaching the 9th disk, while from v1.12.0, the 9th disk would not be scheduled to that node if it only accepts 8 disks totally.

Feedback and Knowledge Base