ji chen

this has been discussed some time ago if I remember correctly, and I don't remember the exact reason @lingxiankong mentioned seems due to time and contribution time etc,

looks like k8s-staging-cloud-provider-ibm and k8s-staging-cloud-provider-gcp are hosting images in the staging repo maybe we can follow that to give a try (but not use it until we are confident enough)

https://github.com/kubernetes/k8s.io/pull/3638

The current info seems too generic >>>A TCPDump suggests that the pod tries to resolve the wrong URL. It will try to connect to ${URL}.kube-system.svc.cluster.local. looks like it's not CPO...

from context, looks like the URL is taken as short service name and appended local host domain name so it's CSI issue instead likely to be a k8s or your...

are you able to connect to the openstack endpoint from your local ? e.g the DNS with the cloud.conf you used?

Original issue is `So I see the same strange thing that was reported above. The container seems to be trying to resolve this address with ".kube-system.svc.cluster.local" appended to the valid...

I don't know the meaning of `register` as this new case is brand new to me ,can you point me where's use case or detailed info? anyway, https://github.com/kubernetes/cloud-provider-openstack/blob/master/pkg/csi/cinder/nodeserver.go#L462 is the...

ok, understand ,so you want to have a way to bypass that process .. I am not manila expert so I don't know the reason why manila use a nodeid...

+1 to introduce this so one k8s cluster in mutliple region is the use case, correct? And I think we need consider backward compatible as well