Resolve "Add functionality to package & Wrapper to specify HR Namespace"
Package Merge Request
Package Changes
Allow for us to specify helmRelease namespaces, which can potentially facilitate future use for when we intend to have different "levels of maintainence"
Package MR
d functionality to package & Wrapper to specify HR Namespace.
For this issue I will need to extensively test it with the following
packages:
crossplane:
enabled: true
git:
repo: https://repo1.dso.mil/big-bang/product/community/crossplane.git
path: "./chart"
tag: "1.15.0-bb.0"
dependsOn:
- name: monitoring
namespace: bigbang
values:
webhooks:
enabled: false
confluence:
enabled: true
namespace:
name: confluencetest
git:
repo: https://repo1.dso.mil/big-bang/product/community/confluence.git
path: "./chart"
tag: "1.20.0-bb.9"
dependsOn:
- name: monitoring
namespace: bigbang
values:
serviceAccount:
name: test
jira:
enabled: true
helmRelease:
namespace: bigbang
namespace:
name: hello
git:
repo: https://repo1.dso.mil/big-bang/product/community/jira.git
path: "./chart"
tag: "1.20.0-bb.3"
values:
jira:
service:
port: 8080
gitlab-ci-pipelines-exporter:
enabled: true
helmRelease:
namespace: bigbang
git:
repo: https://repo1.dso.mil/big-bang/apps/sandbox/gitlab-ci-pipelines-exporter.git
path: "./chart"
tag: "0.3.4-bb.2"
dependsOn:
- name: monitoring
namespace: bigbang
values:
redis:
enabled: false
istio:
enabled: true
config:
gitlab:
url: "https://repo1.dso.mil"
token: ""
enable_health_check: false
health_url: "https://repo1.dso.mil"
For Issue
Closes (link to issue here)
Upgrade Notices
N/A
Closes #2205 (closed)
Merge request reports
Activity
added kindfeature priority5 statusdoing teamPipelines & Infrastructure labels
assigned to @jeffv
added 1 commit
- 7b871605 - add in namespace and targetspace changes for package and wrapper
It works as intended; the deployments don't deploy due to kyverno, except the gitlab-ci-pipeline-exporter, that is due to me not providing a valid gitlab token.
Edited by Jeffrey Victoradded statusreview label and removed statusdoing label
requested review from @chris.oconnell, @andrewshoell, and @michaelmartin
requested review from @mike.knight
added community-contribution label
removed community-contribution label
- Resolved by Andrew Shoell
does the wrapper gitrepo need this same logic?
added statusdoing label and removed statusreview label
added statusreview label and removed statusdoing label
mentioned in commit 768d7a9b