Initial Configuration for Integrations

Configure the Kubernetes connector, namespace, and Docker settings required to run catalog discovery integrations in Harness IDP.

Before you create catalog discovery integrations (say GitHub, PagerDuty, SonarQube and many more), you need to configure the infrastructure that runs the data collection tasks.

This is a one-time setup done from the Integrations section of IDP, and can be updated at any time.

POINTS TO REMEMBER

• If you attempt to create an integration without completing this initial configuration, your integration will not be created. Additionally, you may see an Infra configuration required notification in the Integrations section.

• Platform integrations like Harness CD run directly and do not require this setup.

• Custom Integrations do not require this setup either. Your systems push data to Harness, so no data collection runs in your cluster.

Access the configuration

1. In Harness IDP, go to Configure → Integrations.

2. Click the Configuration button at the top.

   
3. The Infra Configuration panel opens with three steps in the sidebar: Kubernetes Configurations, Docker Configurations, and Sync Configurations.

   

---

Kubernetes configurations

Data collection for each integration runs as pods inside your Kubernetes cluster. IDP sends collection tasks to a delegate running in your cluster, which executes them using credentials stored in your own environment. The Kubernetes Configurations tell IDP which cluster and namespace to use for these pods.

1. In the K8s Connector field, pick an existing connector from your account or click + New Connector to create one. Go to Add a Kubernetes Cluster Connector to create a Kubernetes connector.

2. After selecting the connector, enter the Namespace where data collection pods will be spun up. This is a Kubernetes namespace and must already exist in the cluster before you configure this.

   The Harness delegate you are using (the one you set up when you created your K8s connector in Harness) must have permissions on this namespace.

3. Click Continue to proceed to Docker Configurations.

---

Docker configurations

Data collection pods run as containers that need images to start. By default, IDP pulls these images from the public Harness container registry.

Docker Configurations can only be configured at the account level and are not editable at the organization or project scope.

All fields in this section are optional. Configure them if any of the following apply:

• Rate limiting: Without credentials, Docker Hub throttles unauthenticated pulls after a number of requests. A Docker connector with credentials bypasses this limit.

• Private registry: If your organization's security policy prohibits pulling from public Docker Hub, you can mirror the required images to your private registry and point IDP to it here.

1. In the Docker Connector field, select an existing Docker Registry connector or click + New Connector to create one. Go to Add a Docker Registry Connector to create a Docker Registry connector.

2. Under Connector images, you can specify custom image pull paths for these components:

   • Individual Connector Images (Bitbucket Cloud, GCP, GitHub, Datadog, Dynatrace, PagerDuty, ServiceNow, SonarQube): Only specify image paths (sample format: <your-registry-url>/<image-name>:<image-tag-version>) for the integrations you actually use. Leave all others blank.

   • Lite Engine and Addon: These two components are a must for every data collection run. IDP pulls them from the public Harness registry. If you do not wish to use the public images or your environment cannot access public Docker Hub, you must provide your custom image paths for these two components.

     
3. Click Continue to proceed to Sync Configurations.

---

Sync Configurations

Sync Configurations can only be configured at the account level and are not editable at the organization or project scope.

This is an optional configuration.

By default, integration sync data travels through the default endpoint (i.e., accounts.harness.io, app.harness.io, or app3.harness.io). This section lets you override that behavior if your network restricts outbound traffic to your account's vanity URL only.

1. Toggle on the Use vanity URL for sync traffic checkbox if your network whitelists your custom vanity URL (e.g., yourcompany.harness.io) and does not allow the default endpoint.

   Once enabled, the sync traffic routes through your vanity URL. No manual URL input is needed.

   If your account has no vanity URL configured, the default endpoint is used regardless of this setting.

2. Click Save.

The initial configuration is now complete and you may create your integrations successfully.