-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Labels
bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Description
Description
- I attempted to use the helm chart to install newrelic into a k8s cluster.
- I want the newrelic code in its own namespace, "newrelic"
- I'm using the default certificate system
- The install fails because it attempts to install the certificate secret into the default namespace.
- The controls I have set up do not allow that, and I won't bend them to fit.
Expected Behavior
I expected everything in the newrelic helm chart to install into the specified newrelic namespace.
Troubleshooting or NR Diag results
It looks to me as though the problem could be to do with the use of the k8s-webhook-cert-manager.
The workaround I found was to not use the helm chart, and instead to use a generated manifest yaml.
Steps to Reproduce
apiVersion: "kustomize.config.k8s.io/v1beta1"
kind: "Kustomization"
namespace: "newrelic"
resources:
- "namespace.yaml"
helmCharts:
# ref: https://docs.newrelic.com/install/kubernetes/?dropdown1=helm
- name: nri-bundle
releaseName: newrelic-bundle
# version: "5.15.4"
repo: https://helm-charts.newrelic.com
valuesFile: values-newrelic.yamlYour Environment
Include as many relevant details about your environment as possible including the running version of New Relic software and any relevant configurations.
Additional context
Add any other context about the problem here. For example, relevant community posts or support tickets.
For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
Suggested T-Shirt size (S, M, L, XL, Unknown):
Metadata
Metadata
Assignees
Labels
bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.