It appears that the same DMaaP data router component (docker version 1.3.3 in Casablanca) is being used by 2 project teams: POMBA and A&AI. As such, it would seem that a better way forward (then to update 2 different Helm Charts) would be to create a common "shared" data-router component. This common component can be referenced by the Helm Charts that use it in the requirements.yaml.

Note: it was first thought that this was the same data router that is owned by the DMaaP project. It has been clarified that it is not the same component. As such DMaaP will not make use of this "shared" data-router component. I'm including DMAAP as a tag for the defect to keep them in the loop on how this data router differs and/or relates to DMaaP, if at all. 

Raised on TSC:

From Kenny Paul (LFN) to Everyone: (09:48 AM)

Mike Elliott recommends moving to common
#action Mike E open a jira to move content to common for dublin release
#topic LFIT