# Problems setting up Drone on kubernetes running in private AWS VPC

**URL:** <https://drone.discourse.group/t/problems-setting-up-drone-on-kubernetes-running-in-private-aws-vpc/9512>\
**Category:** Drone Support\
**Created:** [November 3, 2017, 9:20am UTC](https://drone.discourse.group/t/problems-setting-up-drone-on-kubernetes-running-in-private-aws-vpc/9512 "2017-11-03T09:20:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jakst](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/jakst/32/3998_2.png) [@Jakst](https://drone.discourse.group/u/Jakst)\
**Post date:** [November 3, 2017, 9:20am UTC](https://drone.discourse.group/t/problems-setting-up-drone-on-kubernetes-running-in-private-aws-vpc/9512/1 "2017-11-03T09:20:10Z")

</div>

I have a kubernetes cluster running in a private VPC on Amazon.

However, deploying Drone in this cluster leads to this issue: [couldnt-resolve-host-on-clone](http://discuss.harness.io/t/couldnt-resolve-host-on-clone/281/21). It doesn’t matter if I use weave-, flannel- or calico-networking.

There is a workaround mentioned in the comments of that thread, but unfortunately manually applying changes to iptables is not an option in this case.

Is there a way to configure the **deployment of Drone** , or configuring the **initial setup** of the cluster (using **kops** ), so that the build agents can resolve external hosts in a private VPC running kubernetes?

Just to be clear, the goal here is to not have to manually adjust anything after the cluster is set up and Drone is deployed.

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [November 3, 2017, 6:49pm UTC](https://drone.discourse.group/t/problems-setting-up-drone-on-kubernetes-running-in-private-aws-vpc/9512/2 "2017-11-03T18:49:32Z")

</div>

The recommended configuration is to run docker:dind in the same pod as the agent. For some this has resolved the networking issues.

See [Builds fail to resolve bitbucket.org during git clone while running on kops Kubernetes](http://discuss.harness.io/t/builds-fail-to-resolve-bitbucket-org-during-git-clone-while-running-on-kops-kubernetes/617/3)

I am going to close this in favor of one of the existing threads we have on this topic (below). I would prefer to keep all discussion in one place to avoid skattering and duplicating discussion.

- [Couldn't resolve host on clone](http://discuss.harness.io/t/couldnt-resolve-host-on-clone/281/20)
- [Builds fail to resolve bitbucket.org during git clone while running on kops Kubernetes](http://discuss.harness.io/t/builds-fail-to-resolve-bitbucket-org-during-git-clone-while-running-on-kops-kubernetes/617/3)

There is also an existing docker issue and workaround in the comments. [https://github.com/moby/moby/issues/20037](https://github.com/moby/moby/issues/20037)

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [November 3, 2017, 6:49pm UTC](https://drone.discourse.group/t/problems-setting-up-drone-on-kubernetes-running-in-private-aws-vpc/9512/3 "2017-11-03T18:49:38Z")

</div>