IBM Cloud Private installation behind an HTTP proxy

IBM Cloud Private requires Docker. You must manually install Docker on your boot node. You can either manually install Docker on the rest of your cluster nodes, or the installer can automatically install Docker.

Note: For the node that has an environment proxy, export the relevant hostname and IP address. Run the following command to export the information:

  export NO_PROXY=localhost,127.0.0.1,<cluster_CA_domain>.icp,<ICP ip address/range>

Post-installation proxy configuration

Post-installation, you can edit proxy settings of IBM Cloud Private with the following steps:

  1. From the IBM Cloud Private management console, go to Workloads > Deployments.
  2. In Deployments search for helm-api.
  3. Click Edit.
  4. Look for the following lines:

    {
    "name": "HTTP_PROXY"
    },
    {
    "name": "HTTPS_PROXY"
    },
    {
    "name": "NO_PROXY",
    "value": "<ICP cluster IP>,mycluster.icp,mongodb,platform-identity-provider,localhost,127.0.0.1"
    },
    
  5. Edit the HTTP_PROXY and HTTPS_PROXY as appropriate.

    {
    "name": "HTTP_PROXY",
    "value": "http://1.2.3.4:3128"
    },
    {
    "name": "HTTPS_PROXY",
    "value": "http://1.2.3.4:3128"
    },
    {
    "name": "NO_PROXY",
    "value": "<ICP cluster IP>,mycluster.icp,mongodb,platform-identity-provider,icp-management-ingress,iam-pap,localhost,127.0.0.1"
    },
    

    Note: Depending on your environment, the NO_PROXY values may vary. For example, they may include Kubernetes Ingresses and Services resources. It is important that NO_PROXY is fully configured to avoid IBM Cloud Private communicating over the proxy.

    Note: helm-api does not support setting a Proxy-Authorization header. Ensure the proxy is configured so that a Proxy-Authorization header is not required.

  6. Click Submit.

  7. Go to Catalog to check that the Helm charts are shown.