<p>I have an app with several containers running just fine using kubernetes on AWS however now I need to port this to a AWS Dedicated Host VPC where the cluster has previously been created NOT using Kubernetes so I am not able to execute kube-up.sh or its kops equivalent</p>
<p>Is it possible to orchestrate my containers using kubernetes on a pre-existing cluster ? ( IE. have kubernetes probe the parent AWS cluster and treat it as if it created it )</p>
<p>Of course until this linkage is made between my calls to kubectl and the parent AWS Dedicated Host VPC it has no Kubernetes context and just times out :</p>
<blockquote>
<p>kubectl create -f   /my/app/goodie.yaml</p>
<p>Unable to connect to the server: dial tcp 34.199.89.247:443: i/o timeout</p>
</blockquote>
<p>Possible alternative would be to call kube-up.sh or kops and demand the new cluster live inside a specified AWS Dedicated Host ... alas its not apparent Kubernetes has this flexibility ... yet !</p>

<p>Yes, definitely. kubectl is just a client application and it can connect to any kubernetes cluster and orchestrate it. </p>

<p>If you get i/o timeout, you most likely have connectivity issues and some firewall/proxy in place. Did you try to just access the kubernetes API through curl or telnet? </p>
