# Kubernetes Dynatrace-Operator behind firewall and proxy

**URL:** <https://community.dynatrace.com/t/kubernetes-dynatrace-operator-behind-firewall-and-proxy/47924>\
**Category:** Container platforms\
**Tags:** proxy, dynatrace-operator\
**Created:** [September 24, 2024, 5:42am UTC](https://community.dynatrace.com/t/kubernetes-dynatrace-operator-behind-firewall-and-proxy/47924 "2024-09-24T05:42:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![BevanBroun](https://avatars.discourse-cdn.com/v4/letter/b/5daacb/32.png) [@BevanBroun](https://community.dynatrace.com/u/BevanBroun)\
**Post date:** [September 24, 2024, 5:42am UTC](https://community.dynatrace.com/t/kubernetes-dynatrace-operator-behind-firewall-and-proxy/47924/1 "2024-09-24T05:42:20Z")

</div>

Hi All

Im very new to Dynatrace and Kubenetes

We have an activegate and I have installed one agent on several VMs. Everything is going via the proxy and working.

However, Im having lots of trouble getting the monitoring of kubenetes working - most of the issue are about proxy and firewalls. What I would really love is the method of downloading separately so I can avoid these issues.

Eg: The instructions say “helm install dynatrace-operator oci://public.ecr.aws/dynatrace/dynatrace-operator” however despite adding&nbsp;public.ecr.aws to our proxy and firewall rules the traffic doesnt flow, we see from packet capture its being forwarded to another address - so we add that too and we still get nowhere.

At the moment I have downloaded the content from:&nbsp;[Releases · Dynatrace/dynatrace-operator (github.com)](https://github.com/Dynatrace/dynatrace-operator/releases/)&nbsp;and run

```markup
kubectl create namespace dynatrace
kubectl apply -f kubernetes.yaml
apply -f kubernetes-csi.yaml

```

However, as expected the things are trying to download:

```markup
[root@prod-k8s-mast-n1a ~]# kubectl get pods -n dynatrace
NAME READY STATUS RESTARTS AGE
dynatrace-oneagent-csi-driver-69v9k 0/4 Init:ImagePullBackOff 0 19m
dynatrace-oneagent-csi-driver-b94zd 0/4 Init:ImagePullBackOff 0 19m
dynatrace-oneagent-csi-driver-gwqx8 0/4 Init:ImagePullBackOff 0 19m
dynatrace-oneagent-csi-driver-hzt7m 0/4 Init:ImagePullBackOff 0 19m
dynatrace-oneagent-csi-driver-ll4l9 0/4 Init:ImagePullBackOff 0 19m
dynatrace-oneagent-csi-driver-w7n2l 0/4 Init:ImagePullBackOff 0 19m
dynatrace-oneagent-csi-driver-z9sg4 0/4 Init:ImagePullBackOff 0 19m
dynatrace-operator-94d65c56c-k8xx6 0/1 ImagePullBackOff 0 19m
dynatrace-webhook-56bd655b8b-4rzhc 0/1 ImagePullBackOff 0 19m
dynatrace-webhook-56bd655b8b-h6hv4 0/1 ImagePullBackOff 0 19m

```

How can I do this in an offline mode

OR

tell this system to use a proxy and what URLs are needed in firewalls and proxy ACLs?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [September 24, 2024, 6:21am UTC](https://community.dynatrace.com/t/kubernetes-dynatrace-operator-behind-firewall-and-proxy/47924/2 "2024-09-24T06:21:19Z")

</div>

[@BevanBroun](https://community.dynatrace.com/user/81079)&nbsp;you need to copy the images to your local repository, where your k8s can download images as your environment cannot access public repositories directly. See&nbsp;[Store Dynatrace images in private registries — Dynatrace Docs](https://docs.dynatrace.com/docs/shortlink/prepare-private-registry)&nbsp;for details on how to copy images.

After you have images in your repository, follow the steps here:&nbsp;[Use a private registry — Dynatrace Docs](https://docs.dynatrace.com/docs/shortlink/use-private-registry)&nbsp;for deploying&nbsp;the Dynatrace operator in an air-gapped environment.

---

<div class="post-metadata">

**Author:** ![BevanBroun](https://avatars.discourse-cdn.com/v4/letter/b/5daacb/32.png) [@BevanBroun](https://community.dynatrace.com/u/BevanBroun)\
**Post date:** [September 25, 2024, 7:46pm UTC](https://community.dynatrace.com/t/kubernetes-dynatrace-operator-behind-firewall-and-proxy/47924/3 "2024-09-25T19:46:55Z")

</div>

Thanks Julius - Ill be trying this shortly. BTW we are not completely air-gapped. The problem is redirects and proxy/firewall/url lists.

---

<div class="post-metadata">

**Author:** ![timothyyara](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/timothyyara/32/16578_2.png) [@timothyyara](https://community.dynatrace.com/u/timothyyara)\
**Post date:** [March 18, 2025, 5:22pm UTC](https://community.dynatrace.com/t/kubernetes-dynatrace-operator-behind-firewall-and-proxy/47924/4 "2025-03-18T17:22:45Z")

</div>

++1 for knowing where/how to add a custom proxy setting into the dynakube.yaml and what needs to be white-listed or excluded from the proxy settings. Right now, we are having similar issues that the webhook is failing:&nbsp;_TLS handshake error from \*IPADDRESS\* remote error: tls: bad certificate_

---

<div class="post-metadata">

**Author:** ![gopher](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/gopher/32/5728_2.png) [@gopher](https://community.dynatrace.com/u/gopher)\
**Post date:** [March 18, 2025, 9:17pm UTC](https://community.dynatrace.com/t/kubernetes-dynatrace-operator-behind-firewall-and-proxy/47924/5 "2025-03-18T21:17:12Z")

</div>

[@timothyyara](https://community.dynatrace.com/user/50837)&nbsp;[@BevanBroun](https://community.dynatrace.com/user/81079)

you can use the no-proxy feature flag. this is used for both Private Repositories and anywhere else that you need the Active Gate to not route to the proxy.&nbsp;[DynaKube feature flags for Dynatrace Operator — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/reference/dynakube-feature-flags)  
\*\*no-proxy is not set in proxy pull secrets (only the credentials and proxy address), and must be set this way.

Example below:

```python
apiVersion: dynatrace.com/v1beta3
kind: DynaKube
metadata:
  name: dynakube
  namespace: dynatrace
  annotations:
    feature.dynatrace.com/no-proxy: ".dynatrace.svc,.myprivaterepo,.amazonaws.com" #private repo
    feature.dynatrace.com/oneagent-initial-connect-retry-ms: "10000"
    feature.dynatrace.com/init-container-seccomp-profile: "true"

```
