Configure delegate proxy settings
All of the Delegates include proxy settings you can use to change how the Delegate connects to the Harness Manager.
By default, the Harness Delegate uses HTTP and HTTPS in its Proxy Scheme settings.
Kubernetes Proxy Settings
The proxy settings are in the
- name: PROXY_HOST
- name: PROXY_PORT
- name: PROXY_SCHEME
- name: NO_PROXY
- name: PROXY_MANAGER
- name: PROXY_USER
- name: PROXY_PASSWORD
PROXY_MANAGER setting determines whether the Delegate bypasses proxy settings to reach the Harness Manager in the cloud. If you want to bypass, enter
In-Cluster Kubernetes Delegate with Proxy
If an in-cluster Kubernetes Delegate has a proxy configured, then
NO_PROXY must contain the cluster master IP. This enables the Delegate to skip the proxy for in-cluster connections.
Subnet Masks not Supported
You cannot use Delegate proxy settings to specify the Cluster Service Network CIDR notation and make the Delegate bypass the proxy to talk to the Kubernetes API.
Harness does not allow any methods of representing a subnet mask.
The mask should be set in the cluster itself. For example:
kubectl -n default get service kubernetes -o json | jq -r '.spec.clusterIP'
Harness supports mTLS authentication on a case-by-case basis. Contact Harness Support to enable it.