search

aws / eks-anywhere

Run Amazon EKS on your own infrastructure 🚀
https://anywhere.eks.amazonaws.com
Apache License 2.0
1.94k stars 277 forks source link

Creating cluster I still get a timeout towards ecr, even though I've configured a private registry #5343

Open AndreasDavour opened 1 year ago

AndreasDavour commented 1 year ago

What happened: Get \"https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml\": dial tcp 65.9.43.57:443: i/o timeout"

What you expected to happen:

I have configured a private registry and I need to do a totally air-gapped installation. How can I make it not look for manifest.yaml on the internet?

How to reproduce it (as minimally and precisely as possible):

eksctl anywhere cluster create yadda yadda.

Anything else we need to know?:

Environment:

vignesh-goutham commented 1 year ago

Hello @AndreasDavour thanks for trying out EKS-A. It looks like you might be running EKS-A in an air-gapped environment. In addition to using a private registry, you might have to provide a proxy configuration for EKS-A cli to access non-docker image artifacts for the create cluster operation. Please refer https://anywhere.eks.amazonaws.com/docs/reference/clusterspec/optional/proxy/

AndreasDavour commented 1 year ago

Well, if you run an air-gapped environment, which I am indeed transitioning towards, use of a proxy is also off the table.

I did find this option in the instructions on deploying on the Snow provider:

eksctl anywhere create cluster \ -f eksa-mgmt-cluster.yaml \ --bundles-override /usr/lib/eks-a/manifests/bundle-release.yaml

Is that the official way of doing air-gapped installations? Then the cluster creation process are doing something more than just pulling images from a registry, I take it?

AndreasDavour commented 1 year ago

I have not found any section of the iocs that describe all procedures needed for an air-gapped installation, valid for all providers. That might be a good addition.