Communication requirements

CAST AI Deployments and DaemonSets

For the CAST AI components to communicate with CAST AI SaaS, use the following:

CAST AI us console

CAST AI eu console

If it's not possible to add DNS to allow-list on your outbound infrastructure (firewall, NAT, Security Group etc), it is possible to add dedicated IPs:

Use CAST AI components behind a proxy

If your company is using a proxy to access resources at the public network (like ), you need to configure the PROXY variables for the CAST-AI components

Example: castai-agent deployment on GKE cluster:

                - env:
                    - name: API_URL
                    - name: PROVIDER
                      value: gke
                    - name: MONITOR_METADATA
                      value: /agent-metadata/metadata
                    - name: PPROF_PORT
                      value: "6060"
                    - name: HTTP_PROXY
                      value: "http://<proxyaddress>:<port-if-needed>"
                    - name: HTTPS_PROXY
                      value: "https://<proxyaddress>:<port-if-needed>"
                    - name: NO_PROXY
                      value: "localhost,<pod cidr><svc cidr>,*.cluster.local,,"
                    - secretRef:
                        name: castai-agent

Add the environment variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY to the castai-agent deployment.

Make sure that NO_PROXY has set the correct settings matching to your environment to prevent sending Kubernetes-internal traffic to the external proxy!

Container Registry to pull images

Helm charts

Node binaries

Node startup logs upload

This includes kubelet, driver errors, etc.