Proxy setup for ELK

If you are running in an isolated environment and need to access Internet via a http(s) Proxy, please merge the following code to your custom-values.yaml outside of the global section.

monitoring:
  statefulSets:
    elastic-agent-apm:
      env:
        HTTP_PROXY: "http://<proxy_server_host>:<port>"
        HTTPS_PROXY: "http://<proxy_server_host>:<port>"
        NO_PROXY: "localhost,127.0.0.1,.<company_tld>,<hostname>,<ip_of_host>,<ip_of_gateway>"
  daemonSets:
    elasticagent:
      env:
        HTTP_PROXY: "http://<proxy_server_host>:<port>"
        HTTPS_PROXY: "http://<proxy_server_host>:<port>"
        NO_PROXY: "localhost,127.0.0.1,.<company_tld>,<hostname>,<full_hostname>,<ip_of_host>,<ip_of_gateway>,.svc.cluster.local,kube-state-metrics-service-headless,rabbitmq-service-headles.<namespace>.svc.cluster.local"

Items for explanation: . company_tld: (optional) If your environment is within a company environment and has direct access without proxy, you can add this here. There is a dot before the TLD string. . hostname: (required) the hostname of the current server . ip_of_host: (required) the IP address of the host that runs the Kubernetes cluster . ip_of_gateway: (optional) depend on what Kubernetes flavour used, usually it should be the gateway address of the cni0 ethernet hardware . namespace: the namespace of the RabbitMQ cluster

The hostnames of the remote-rabbitmq Kubernetes services in the same Kubernetes cluster should be in the NO_PROXY environment variable. If you have multiple RabbitMQ clusters in the same environment, add them as well.