Goal

Today we have a custom fork of a volume populator library, which we need to manually maintain and keep up with the Kubernetes upstream.

After this epic, we should move to the official upstream and work with the upstream maintainers of the volume populator to expand whatever we to the general solution.

User Stories

• As a maintainer of MTV, I don't want to manually maintain a fork of an external library so that we don't need to worry about the different libraries' huge differences causing future issues. 
• As a maintainer of MTV, I don't want to deal with the CVE fixes by manually fixing the code in our for lib.

Non-Requirements

• We should not force all changes that we did in the lib to the upstream, we should adapt our code to the upstream and expand it with only a general solution if absolutely necessary