If you are running our Kuberenetes integration with a proxy, you need to configure each component (the infrastructure agent, logging, Kubernetes events, etc.) to correctly work with your proxy.
Install the infrastructure agent with a proxy
There are three options to install the infrastructure agent with a proxy:
- Installing with chart
newrelic-infrastructure
:- The proxy can be configured setting the configuration option
config.proxy
as described in the values.yaml of the chart.
The wholeconfig
object is used to generate a configMap that is mounted as the file /etc/newrelic-infra.yml used to configure the agent.
- The proxy can be configured setting the configuration option
- Installing with chart
nri-budle
as a dependency:- The proxy can be configured setting the configuration option
newrelic-infrastructure.config.proxy
. The configuration option is passed down to the dependencynewrelic-infrastructure
modifying thevalues.yaml
ofnri-bundle
:newrelic-infrastructure.config.proxy: https://user:password@hostname:port
- The proxy can be configured setting the configuration option
- Installing with manifest:
- When installing through the manifest, the proxy can be configured adding the
NRIA_PROXY
environment variable to the environment variable section of the DaemonSet configuration. - The environment variable
NRIA_VERBOSE
in the DaemonSet YAML can be used as an example of the environment variable configuration.
- When installing through the manifest, the proxy can be configured adding the
Set logging with a proxy
If you’re using log forwarding for the Kubernetes integration, the plugin automatically detects the HTTP_PROXY
and HTTPS_PROXY
environment variables, and automatically uses them to set up the proxy configuration. For more information, see how to customize the proxy, or bypass it.
Install Kubernetes events
There are three options to install the Kubernetes events integration with a proxy:
- Installing with chart
nri-kube-events
:- The proxy can be configured setting the configuration option
proxy
in the values.yaml file. If set, the variableNRIA_PROXY
will be added into the deployment.yaml template.
- The proxy can be configured setting the configuration option
- Installing with chart
nri-budle
as a dependency:- The proxy can be configured setting the configuration option
nri-kube-events.proxy
. The configuration option is passed down to the dependencynri-kube-events
modifying thevalues.yaml
ofnri-bundle
:nri-kube-events.proxy: https://user:password@hostname:port
- The proxy can be configured setting the configuration option
- Installing with manifest:
- When installing through the manifest, to configure the proxy set the
NRIA_PROXY
in the environment variable section of the infra container. - Check the deployment template of the chart as an example of environment variable configuration.
- When installing through the manifest, to configure the proxy set the
Install the Prometheus OpenMetrics integration
There are three options to install the Prometheus OpenMetric integration with a proxy:
- Installing with charts
nri-prometheus
:- The proxy can be configured setting the configuration option
config.emitter_proxy
in the values.yaml.
Theconfig
object is used to generate a configMap that mounted into the deployment under/etc/nri-prometheus/
.
- The proxy can be configured setting the configuration option
- Installing with chart
nri-budle
as a dependency:- The proxy can be configured setting the configuration option
nri-prometheus.config.emitter_proxy
. The configuration option is passed down to the dependencynri-prometheus
modifying thevalues.yaml
ofnri-bundle
:nri-prometheus.config.emitter_proxy: "http://localhost:8888
- The proxy can be configured setting the configuration option
- Installing with the manifest:
- Configure the proxy uncommenting the
emitter_proxy
option directly in the manifest:# Proxy to be used by the emitters when submitting metrics. It should be # in the format [scheme]://[domain]:[port]. # The emitter is the component in charge of sending the scraped metrics. # This proxy won't be used when scraping metrics from the targets. # By default it's empty, meaning that no proxy will be used. # emitter_proxy: "http://localhost:8888"
- Configure the proxy uncommenting the
Set the synthetics minion
Check this README on how to set the proxy for the Synthetics minions.