Kubesense

Networking & Firewall Rules

Configure networking and firewall rules to enable communication between KubeSense components and external services.

Server-Sensor Ports

The following ports must be open between the KubeSense server and sensor components:

ComponentPortPurposeFirewall Rule
Kubecol Controller32033Kubernetes info and infrastructure attributesAllow inbound from kubesensors
Kubecol Ingestor32133Trace processing and database ingestionAllow inbound from kubesensors
Metrics Collector30060Infrastructure metrics (CPU, memory, etc.)Allow inbound from otel-agent
Events Port30051Kubernetes event informationAllow inbound from otel-agent
Log Aggregator30052Log processing and transformationAllow inbound from logsensors

External Services

The following outbound connections are required:

ServiceEndpointPortPurpose
ECR Registry365639915496.dkr.ecr.us-east-1.amazonaws.com443Pull container images
Amazon SESemail.ap-south-1.amazonaws.com443Email notifications
AWS STSsts.amazonaws.com443Secure token management
AWS Sign-insignin.aws.amazon.com443Authentication

Summary

Ensure the following are configured:

  1. Internal ports (32033, 32133, 30060, 30051, 30052) are open between server and sensor nodes
  2. Outbound HTTPS (port 443) is allowed to the ECR registry and AWS services listed above