ji chen

>>>With k8s 1.23.x and cloud-provider-openstack 1.23.x if we pass "--cloud-provider=external" along with "--node-ip=10.0.16.2" as KUBELET_EXTRA_ARGS to the kubelet.service file we observe that the Node.status.addresses was as follows I didn't see...

>>>But for PODs kube-apiserver-master-, kube-controller-manager- and kube-scheduler- if we describe the pods, um.. I think at least the pod IP doesn't belong to CPO scope , CPO only focus on...

I think it's a function gap , I knew we have barbican usage in ingresss and kms but CSI we seems don't have this at all I am not expert...

yes, saw the history https://github.com/kubernetes/cloud-provider-openstack/issues/1864 now and will keep read this , in case any gap or Doc change, will discuss and propose PR, thanks for all the detailed info~

Thanks for the detailed info ,so maybe you can assign yourself on this @nashford77 as you seems already have a solution :)

This is weird.. LB is a VM with pre-installed haproxy by default and the ip 1.2.1.214 should be the ip of the LB I knew we had a sec group...

>>>Failed to create an OpenStack Secret client: unable to initialize keymanager client for region RegionOne: No suitable endpoint could be found in the service catalog. this is ok, as it...

the log provided seems truncated ,and nothing special until `I0522 13:46:34.568918 ` which is last log I can see.. have you tcpdump on the VM to anything wrong there? beyond...

I think https://docs.openstack.org/devstack/latest/guides/devstack-with-lbaas-v2.html might be the easiest way to go..

/test openstack-cloud-csi-cinder-e2e-test