New upstream names containers inside pods as upstream

[p1-bot-repo-sync]

Possible bug.

With the update for applications to use upstream, I have noticed their are appliation pods with the containers inside them named upstream (Jira, Confluence, Grafana, and External Secrets Operator).

The only item I have found is in the chart.yaml file where alias is being used (https://repo1.dso.mil/big-bang/product/maintained/jira/-/blob/main/chart/Chart.yaml?ref_type=heads#:~:text=main/charts/jira-,alias%3A%20%22upstream%22,-UNCLASSIFIED%20%2D%20NO%20CUI).

[p1-bot-repo-sync]

michaelmartin commented:

---

Hi @carawanc ! As a temporary fix, you can add these values to your overrides to change the name:

packages:
  jira:
    values:
      upstream:
        jira:
          useHelmReleaseNameAsContainerName: true
        common:
          nameOverride: jira
          fullnameOverride: jira

We will add these values as defaults to maintain the prior-passthrough behavior.

Thanks, for reporting this!

[p1-bot-repo-sync]

michaelmartin commented:

---

Hi @carawanc ! As a temporary fix for jira, you can add these values to your overrides to change the name:

packages:
  jira:
    values:
      upstream:
        jira:
          useHelmReleaseNameAsContainerName: true
        common:
          nameOverride: jira
          fullnameOverride: jira

We will add these values as defaults to maintain the prior-passthrough behavior for jira. We'll also need to look at the other charts too there and see if we can do a similar fix.

Thanks, for reporting this!

[p1-bot-repo-sync]

carawanc commented:

---

Thank you,
The work around seems to be working for Jira and Confluence. I will work on testing the work around on other products on our side.