(rbd) github page speaks about a pod network issue around netNamespaceFilePath, can helm chart just implement the solution?

[lknite]

Describe the feature you'd like to have

It's not clear to me just yet what the pod network issue is documented which is related to netNamespaceFilePath. Maybe I'll get it after I read it a few more times. In the meantime, could the helm chart not just implement the suggested solution?

What is the value to the end user? (why is it a priority?)

If the helm chart could just implement the solution. Or a 2nd helm chart? Then I wouldn't really even need to know about the race condition / pod networking issue. Sounds like there is a solution. Would be nice to just get the solution without having to know all the details. Isn't this something everyone would want to have ... so we could all just get it without having to do additional steps. I commented out the netNamespaceFilePath value, not sure if that disables the work around or enables a work around?

I'd just like it to be automatic. Its ok even if I have to install another helm chart. ... though the helm chart itsself could just include a dependency on a 2nd helm chart with the work around. A field in the helm chart could enable the work-around by default and include a comment to an explanation as to what its actually doing behind the scenes.

How will we know we have a good solution? (acceptance criteria)

When its no longer necessary to add the race condition information to the README page on github cause the work-around is already in place. Or just mention the work-around as needed so we can avoid restarting that thing.