Instana EUM javascript generated incorrectly in Open Shift helm deployment

[jdday001]

Deploying Robot Shop to Open Shift using the helm chart generates incorrect EUM javascript, causing Instana EUM reporting to fail.

This is the debug from running the helm chart. Note that the eum.url value passed has the trailing slash.
Release "robot-shop" has been upgraded. Happy Helming!
NAME: robot-shop
LAST DEPLOYED: Thu Oct  7 09:27:40 2021
NAMESPACE: robot-shop
STATUS: deployed
REVISION: 2
TEST SUITE: None
USER-SUPPLIED VALUES:
eum:
  key: XXXXXXXXXXXXXXXXXXXXX
  url: https://instana-eum.XXXXXX.XXXXX.com/eum/
ocCreateRoute: true
openshift: true

The helm chart deployment results in this eum.html page being created in the container. Note that the trailing slash has been droped from reportingUrl.

<script>   (function(s,t,a,n){s[t]||(s[t]=a,n=s[a]=function(){n.q.push(arguments)},   n.q=[],n.v=2,n.l=1*new Date)})(window,"InstanaEumObject","ineum");   ineum('reportingUrl', 'https://instana-eum.XXXXXX.XXXXX.com/eum');   ineum('key', 'XXXXXXXXXXXXXXXXXXXXX');   ineum('trackSessions');   ineum('page', 'splash'); </script> <script defer crossorigin="anonymous" src="https://instana-eum.XXXXXX.XXXXX.com/eum/eum.min.js"></script>

As a result, Robot Shop does not transmit data to Instana EUM. After modifying eum.html in the running container to add the trailing slash to reportingUrl, EUM data begins appearing in Instana.

This is using the most recent commit in the master branch.

$ git log
commit b1adf4c (HEAD -> master, origin/master, origin/HEAD)
Author: SteveWW [email protected]
Date: Wed Sep 1 12:27:45 2021 +0100