Networking

Use the information on this page to configure different networking settings in Chronosphere Telemetry Pipeline.

Ports

Pipelines expose various ports to send and receive data. These ports correspond to different components of each pipeline.

View exposed ports for a pipeline

To view a list of exposed ports for a pipeline, use the following command:

calyptia get endpoints --pipeline PIPELINE

Replace PIPELINE with the name of your pipeline.

Inputs and outputs

Most source plugins and some destination plugins expose an associated port. Plugins that expose a port will set a default value for that port, but you can override this value when you configure plugins through the Telemetry Pipeline web interface or through pipeline configuration files.

Health check pipelines

The health check pipeline within each Core Instance exposes an HTTP server on TCP port 2020.

Uniqueness

For all pipelines within a single Core Instance, each open port must use a unique port number and protocol. This restriction applies to components within the same pipeline and components across different pipelines. However, different components can share a port number if one component uses TCP and another uses UDP.

For example, if Pipeline A and Pipeline B belong to the same Core Instance, both pipelines can’t have a source plugin that exposes TCP port 1600, but Pipeline A can expose TCP port 1600 and Pipeline B can expose UDP port 1600. Similarly, Pipeline C can’t have two different source plugins that both expose TCP port 1850, but it can have one plugin that exposes TCP port 1850 and another plugin that exposes TCP port 1851.

Proxies

You can use an HTTP proxy to route traffic between a Core Instance and any connected services. To do so, use the following command:

calyptia update core_instance operator INSTANCE --http-proxy=PROXY

Replace the following values:

• INSTANCE: The name of your Core Instance.
• PROXY: The proxy to use (for example, http://localhost:3128).

You can also specify an HTTPS proxy with the https-proxy flag.

Service types

Each pipeline uses one of the available Kubernetes Service (opens in a new tab) types. The Service types supported by Telemetry Pipeline are:

• ClusterIP (opens in a new tab)
• LoadBalancer (opens in a new tab)
• NodePort (opens in a new tab)

Create a pipeline with a specific Service type

When creating a pipeline, use the --service-type flag to specify its Service type:

calyptia create pipeline --name PIPELINE --core-instance INSTANCE --service-type TYPE

Replace the following values:

• PIPELINE: A short name you’d like to give your pipeline.
• INSTANCE: The name of your Core Instance.
• TYPE: The Service type for your pipeline (ClusterIP, LoadBalancer, or NodePort).

Modify the Service type of an existing pipeline

To modify the Service type of an existing pipeline, use the following command:

calyptia update pipeline PIPELINE --service-type TYPE

Replace the following values:

• PIPELINE: The name or unique ID of your existing pipeline.
• TYPE: The Service type for your pipeline (ClusterIP, LoadBalancer, or NodePort).