Tracking/Discussion: How can we better deal with regressions on ASH?

[theobarberbany]

Currently we don't test ASH - it's difficult as it's an on prem solution. However, because we use the cloud providers for instances where we're running kube on ASH, changes to cloud-provider-azure can break ASH without us realising.

It would be great to get early (pre merge? if possible) signal if a change impacts ASH, to avoid having to either revert changes or add ASH specific bug fixes later.

#9704

(not in cloud provider azure, but the same root problem, which is lack of ASH signal before merge)

https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/3428/files
kubernetes-sigs/azuredisk-csi-driver#3449

[nilo19]

what is ash? does ash has a ci test to guard when you try to bump cloud-provider-azure version?