Air gap support
What would you like to be added: We need air gap support for users who want disconnected environments.
I think #98 is a step towards full airgapped support. We also have http_proxy support for customers in a not fully locked down environment.
anywhere-assets.eks.amazonaws.com (to download the binaries, manifests and OVAs) distro.eks.amazonaws.com (download manifest and probably some binaries like kubelet and kubectl)
We need air gap support as well for disconnected environment.
Offline deployments seem to be working now using v0.7.2. https://github.com/aws/eks-anywhere/issues/1373#issuecomment-1059707796
For anyone who lands on this issue, EKS Anywhere currently supports proxy configuration as well as local registry configuration that will allow users to create clusters in disconnected environments.
Related https://github.com/aws/eks-anywhere/blob/main/designs/air-gapped.md
With version 0.14.1 private registries work correctly with self-signed certificates in airgapped environments. However, proxy is not working correctly on master/workers nodes. Even if it's specified in configuration yaml, it's still not able to pull images from public registries
With version 0.14.1 private registries work correctly with self-signed certificates in airgapped environments. However, proxy is not working correctly on master/workers nodes. Even if it's specified in configuration yaml, it's still not able to pull images from public registries
@Paulius0112 we don't support proxy for baremetal yet. That will be added in this PR https://github.com/aws/eks-anywhere/pull/4869