Support Center > Search Results > SecureKnowledge Details
Troubleshoot the onboarding of Kubernetes clusters to CloudGuard Dome9 Technical Level


Use these troubleshooting hints to resolve problems in deploying the agent.

Check that the pod was created

kubectl -n [namespace] get pods

If the pod was not created correctly (e.g. it exists but is not ready), get pod details:

kubectl describe -n [namespace] pod [pod_name]

Check the Kubernetes logs

Use this command to get the logs:

kubectl -n [namespace] logs [pod_name]

Check if there are any errors in the logs.

Check the connectivity from the pod 

The pod must have HTTPS (port 443) connectivity to Dome9 (

Check these entities for possible configuration issues that prevent connectivity to the agent:  Proxy, Network Policy, Security Groups, and FW rules.

 You can install another pod that has curl (such as an Ubuntu pod for example) in the same namespace, with the same labels, exec into it and check connectivity to Dome9 using curl.

curl -k -X POST

If there is connectivity with the agent, the response will be {"message":"Unauthorized"}.

Connectivity to Image Registry

The node needs HTTPS (port 443) connectivity to the Quay registry. If you see an image pull error,  check the connectivity to

Kubernetes behind a gateway

If your cluster is located behind a gateway performing HTTPS inspection, try to create a bypass rule for and*, and retest. If the bypass rule resolves the issue, it indicates that the CA certificate  to pods of the flow-logs daemonset should be mounted. The path should be /ca_custom/custom_ca.cer , where the custom_ca.cer file contains the Base64-encoded CA certificate.

Also, if there is a gateway, add a firewall or SG rule to allow access from the agent to the two URLs above (Dome9, and Quay). Docker may also have to be configured with the proxy to allow image downloads from Quay.

Based on your proxy configuration you can use the following environment variable in the deployment (by editing the helm) to enable the proxy on the pod:

value: "http://<proxy-url>:<proxy-port>/"
- name: NO_PROXY
value: "kubernetes.default.svc"

Enable debugging

Edit the deployment, and set the debug level:

kubectl -n [namespace] set env deployment [deployment] LOG_LEVEL=debug

Then, recheck the logs.

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Give us Feedback
Please rate this document