feat(csi-node): allow listening on IPv6 Pod IPs

[michaelbeaumont]

See openebs/mayastor#1731

[tiagolobocastro]

Looks like DCO is failing, please amend commit with signature.
Also I suggest not to add the github smart link on the PR description. We use bors with merge, including PR description so everything a branch is pushed there's a github event on the mentioned ticket. In case someone is push a lot of branches for some reason it floods the github ticket.

[tiagolobocastro]

bors d+

[bors-openebs-mayastor]

✌️ michaelbeaumont can now approve this pull request. To approve and merge a pull request, simply reply with bors r+. More detailed instructions are available here.

[michaelbeaumont]

@tiagolobocastro so only put the link in the commit message?

[tiagolobocastro]

@tiagolobocastro so only put the link in the commit message?

I would suggest leaving it as a comment instead, though now that I think about it, not sure github would then auto close issue in this case.
So feel free to do whatever makes more sense to you.

[michaelbeaumont]

@tiagolobocastro sorry wasn't clear, I think I can put it in the merged commit message without flooding the issue. Hmm actually I guess bors controls that. So there's just never a link back to an issue anywhere?

[michaelbeaumont]

bors try

[bors-openebs-mayastor]

try

Build failed:

• continuous-integration/jenkins/branch

[tiagolobocastro]

sigh:

[2024-10-09T19:16:56.607Z] OpenTelemetry trace error occurred. Exporter otlp encountered the following error(s): the grpc server returns error (The service is currently unavailable): , detailed error message: error trying to connect: tcp connect error: Connection refused (os error 111)

I'm tempted to disable jaeger tracing from the tests...

bors try

[bors-openebs-mayastor]

try

Build succeeded:

• continuous-integration/jenkins/branch

[michaelbeaumont]

bors merge

[bors-openebs-mayastor]

Build succeeded:

• continuous-integration/jenkins/branch