| Metrics | Events | Logs | Traces | Visualization | Automation |
|---|---|---|---|---|---|
| :-: | ✅ | ❌ | ❌ | ❌ | ❌ |
A New Relic Infrastructure deployment example for running New Relic On-Host Integrations in Kubernetes. For Kubernetes performance and state metrics, and most other use cases, customers should use the New Relic Kubernetes integration. The New Relic Kubernetes integration is configured to run the New Relic Infrastructure agent as a Daemonset.
This Singleton should be used instead of the New Relic Kubernetes Integration when:
- The On-Host Integration does not need to run on every Kubernetes worker node
- The On-Host Integration is connecting to an endpoint outside of the cluster (e.g. an RDS database)
Create a secret containing your New Relic license (ingest) key and store it in the same namespace where your deployment will be running.
kubectl create secret generic newrelic-license-key --from-literal=license-key=<NR LICENSE KEY HERE> -n newrelic
After creating your secret, update the configmap.yaml and deploy the agent.
kubectl apply -f ./agent/. -n newrelic
See docs here.
New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR DEDICATED SUPPORT. Issues and contributions should be reported to the project here on GitHub.
We encourage you to bring your experiences and questions to the Explorers Hub where our community members collaborate on solutions and new ideas.
We encourage your contributions to improve the New Relic Infrastructure K8s Singleton! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. If you have any questions, or to execute our corporate CLA, required if your contribution is on behalf of a company, please drop us an email at opensource@newrelic.com.
A note about vulnerabilities
As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.
If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.
New Relic Infrastructure K8s Singleton is licensed under the Apache 2.0 License.