Products | Versions |
---|---|
Spotfire Server | ALL CDK version |
When deploying Spotfire Server on Kubernetes, it may be necessary to route network traffic through an HTTP/HTTPS proxy, especially for external communications like Entra ID (Azure AD) SSO.
This article provides the steps to configure these proxy settings and define no_proxy exceptions to ensure proper communication within the Kubernetes cluster and to specified internal resources used for the Spotfire Server deployed using the cloud deployment kit.
Configuring these settings is crucial for overall Spotfire server functionality when operating behind a proxy.
Spotfire Server deployed using the Cloud Deployment Kit
To configure proxy and no_proxy settings for the Spotfire Server pod in a Kubernetes environment, you should use the extraEnvVars key present in your values.yaml file. This allows you to add additional environment variables to the Spotfire-server pod.
Here are the instructions:
1. Modify your values.yaml file to add the following in the extraEnvVars block of your values.yaml file. Replace the placeholders below with the actual values.
extraEnvVars:
- name: CATALINA_INITIAL_HEAPSIZE
value: <e.g 4G>
- name: CATALINA_MAXIMUM_HEAPSIZE
value: <e.g 8G>
- name: CATALINA_OPTS
value: -Dhttp.proxyHost=<your-proxy-host> -Dhttp.proxyPort=<proxy-port> -Dhttps.proxyHost=<your-proxy-host> -Dhttps.proxyPort=<proxy-port> -Dhttp.nonProxyHosts="localhost|127.0.0.1|10.*.*.*|*.xyz.com"
Note: Ensure the no_proxy value is enclosed in double quotes.
2. After modifying the values.yaml file, apply the changes to your Kubernetes deployment to ensure the new environment variables are picked up by the Spotfire Server pods.
This article explains how to configure HTTP and HTTPS proxy settings, along with no_proxy exclusions, for Spotfire Server deployed on a Kubernetes environment.
Github: Spotfire Cloud Deployment Kit link to additional custom environment variables:
External: Oracle Networking Properties: