# Connectivity issues when using Calico

**URL:** <https://community.dynatrace.com/t/connectivity-issues-when-using-calico/42912>\
**Category:** Troubleshooting\
**Tags:** kubernetes\
**Created:** [November 30, 2023, 12:20pm UTC](https://community.dynatrace.com/t/connectivity-issues-when-using-calico/42912 "2023-11-30T12:20:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![darynakovyrina](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/darynakovyrina/32/30846_2.png) [@darynakovyrina](https://community.dynatrace.com/u/darynakovyrina)\
**Post date:** [November 30, 2023, 12:20pm UTC](https://community.dynatrace.com/t/connectivity-issues-when-using-calico/42912/1 "2023-11-30T12:20:00Z")

</div>

If you use Calico to handle or restrict network connections, you might experience connectivity issues, such as:

- The operator, webhook, and CSI driver pods are constantly restarting
- The operator cannot reach the API
- The CSI driver fails to download OneAgent
- Injection into pods doesn’t work

If you experience these or similar problems, use our [GitHub sample policies for common problems](https://dt-url.net/operator-calico-policies).

Spoiler

- For the `activegate-policy.yaml` and `dynatrace-policies.yaml` policies, if Dynatrace Operator isn’t installed in the `dynatrace` namespace (Kubernetes) or project (OpenShift), you need to adapt the metadata and namespace properties in the YAML files accordingly.

- The purpose of the `agent-policy.yaml` and `agent-policy-external-only.yaml` policies is to let OneAgents that are injected into pods open external connections. Only `agent-policy-external-only.yaml`

- Injection into pods doesn’t work
