calling "https://grafana.github.io/helm-charts" and deploying to default namespace

[arpitmishra-eaton]

Hi Team,

since we are calling grafana-helm chart repo is deploying to "default namespace". and currently blocked our work due to security issue.

we would like you to support us to change the namespace instead of default in kubernetes. here are my configuration, please help!

calling grafana-helmchart repo in prepare.grafana.sh

helm repo add grafana https://grafana.github.io/helm-charts helm repo update

pull external charts

helm pull grafana/grafana --untardir ./external --untar cp grafana-dashboards/* external/grafana/dashboards/

another file for values (grafana_values.yaml)

replicas: 1

image: repository: grafana/grafana

Overrides the Grafana image tag whose default is the chart appVersion

tag: "" sha: "" pullPolicy: IfNotPresent pullSecrets: []

containerSecurityContext: readOnlyRootFilesystem: true

downloadDashboards: securityContext: readOnlyRootFilesystem: true

serviceAccount: autoMount: false

initChownData: enabled: false

testFramework: enabled: false

nodeSelector: agentpool: systempool

tolerations: []

affinity: {}

deploymentStrategy: type: Recreate

persistence: type: pvc enabled: true storageClassName: default accessModes:

• ReadWriteOnce size: 10Gi finalizers:
• kubernetes.io/pvc-protection extraPvcLabels: {}

adminUser: admin

admin: existingSecret: "" userKey: admin-user passwordKey: admin-password

envFromSecret: "timescaledb-datasource"

datasources: datasources.yaml: apiVersion: 1 datasources:

• name: LoadTestMetrics type: postgres url: $PG_HOST user: $PG_USER secureJsonData: password: $PG_PASSWORD jsonData: database: $PG_DB sslmode: 'require' # disable/require/verify-ca/verify-full maxOpenConns: 100 # Grafana v5.4+ maxIdleConns: 100 # Grafana v5.4+ maxIdleConnsAuto: true # Grafana v9.5.1+ connMaxLifetime: 14400 # Grafana v5.4+ postgresVersion: 1407 # 903=9.3, 904=9.4, 905=9.5, 906=9.6, 1000=10 timescaledb: true

dashboardProviders: dashboardproviders.yaml: apiVersion: 1 providers:

• name: 'default' orgId: 1 folder: '' type: file disableDeletion: false editable: true options: path: /var/lib/grafana/dashboards/default

dashboards: default: k6-test-list: file: dashboards/dashboard-tests.json k6-test-run: file: dashboards/grafana_dashboard_timescaledb.json

grafana.ini: paths: data: /var/lib/grafana/ logs: /var/log/grafana plugins: /var/lib/grafana/plugins provisioning: /etc/grafana/provisioning analytics: check_for_updates: true log: mode: console grafana_net: url: https://grafana.net server: domain: "{{ if (and .Values.ingress.enabled .Values.ingress.hosts) }}{{ .Values.ingress.hosts | first }}{{ else }}''{{ end }}"

namespaceoverride: ""

Please let us know where we could change the namespace.

[soloturn]

does

helm upgrade ... --namespace

work?

[arpitmishra-eaton]

Hi - I have tried as below:

helm repo add grafana https://grafana.github.io/helm-charts helm repo update --namespace grafana helm pull grafana/grafana --untardir ./external --untar helm repo rm grafana

post-pull steps

cp grafana-dashboards/* external/grafana/dashboards/

it thorwn an error: Chart.yaml is missing.

so i have added chart.yaml file as below:

apiVersion: v2 name: grafana version: 8.5.1 appVersion: 11.2.0 kubeVersion: "^1.8.0-0" description: The leading tool for querying and visualizing time series and metrics. type: application keywords:

• monitoring
• metric

it passed the pipeline however didnt deploy grafana in kubernetes and still showing namespace as default

output of deploying grafana: Release "grafana" has been upgraded. Happy Helming! upgrade.go:158: [debug] preparing upgrade for grafana NAME: grafana upgrade.go:166: [debug] performing update for grafana LAST DEPLOYED: Wed Sep 11 12:18:01 2024 upgrade.go:364: [debug] creating upgraded release for grafana NAMESPACE: default client.go:393: [debug] checking 0 resources for changes STATUS: deployed upgrade.go:436: [debug] waiting for release grafana resources (created: 0 updated: 0 deleted: 0) REVISION: 77 wait.go:50: [debug] beginning wai