Skip to main content

Documentation Portal

Enable Proxy support

When using TrendMiner, some parts of the application require internet access, such as automated upgrades, licensing, and metric collection.

Important

Proxy configuration is only supported on single node deployments, not on virtual appliance deployments. If you're in doubt about your deployment, see this documentation to check if TrendMiner is deployed as a virtual appliance: How to check if TrendMiner is deployed as a virtual appliance?

Requirements

  • a configured proxy server where the TrendMiner installation has access to.

  • root access (or using sudo) on the TrendMiner server, either over console or over SSH

  • Basic Linux Knowledge (used command: vi/nano/ssh/ls/cd)

  • Proxy server configured with internet access (HTTPS) towards the following urls

    license.trendminer.cloud
download.license.trendminer.cloud
Setup in TrendMiner server

Step 1: Setup EdgeManager to be able to communicate using a proxy

  1. create a proxy config file

    vi /etc/systemd/system/tm-edge-manager.service.d/proxy.conf

  2. add the following content

    [Service]
Environment="http_proxy=login:password@proxyservernameorip:port"
Environment="https_proxy=login:password@proxyservernameorip:port"
Environment="no_proxy=localhost,127.0.0.1,.cluster.local,10.42.0.0/24,10.42.1.0/24,10.41.1.0/24,10.41.0.0/24"
Environment="HTTP_PROXY=login:password@proxyservernameorip:port"
Environment="HTTPS_PROXY=login:password@proxyservernameorip:port"
Environment="NO_PROXY=localhost,127.0.0.1,.cluster.local,10.42.0.0/24,10.42.1.0/24,10.41.1.0/24,10.41.0.0/24"

    Make sure to replace “login:password@proxyservernameorip:port” with the proxy server for your organization.

    Make sure to have your server IP listed in the NO_PROXY and no_proxy variables above also, or add the ip range.

    Environment="NO_PROXY=localhost,IPOFSERVER, ...."
Environment="no_proxy=localhost,IPOFSERVER,....."

    or

    Environment="NO_PROXY=localhost,IPOFSERVER/24, ...."
Environment="no_proxy=localhost,IPOFSERVER/24,....."

  3. reload systemctl deamon and restart EdgeManager to activate the changes

    # systemctl daemon-reload
# systemctl restart tm-edge-manager.service

Step 2: setup kubernetes specific proxies

  1. Login to the the TrendMiner Instance over SSH/Console

  2. Create a file /etc/ansible/facts.d/proxy.factusing vi and add the following content

    {
  "http_proxy": "http://<PROXY_IP>:3128/",
  "https_proxy": "http://<PROXY_IP>:3128/",
  "no_proxy": "SERVERIP,localhost,127.0.0.1,.cluster.local,10.42.0.0/24,10.42.1.0/24,10.41.0.0/24"
}

    Replace or change the following part in this file:

    1. <PROXY_IP>:3128 with the ip and port and authentication of the proxy server to use

    2. replace SERVERIP with the ip or subnet of your server e.g. 10.0.1.5 or 10.0.1.0/24

  3. Save the file

  4. Run configure-tm-platform (this will bring down TrendMiner, and restart it)

    # ansible-playbook /mnt/data/ansible-playbooks/platform/configure-tm-platform.yml

  5. Restart tm-config-operator / tm-metrics-forwarder as following

    # kubectl rollout restart -n tm-config-operator-system deployment.apps/tm-config-operator-controller-manager
deployment.apps/tm-config-operator-controller-manager restarted
# kubectl rollout restart -n tm-metrics-forwarder-system deployment.apps/tm-metrics-forwarder
deployment.apps/tm-metrics-forwarder restarted
In this section: