EKS Anywhere cluster installation fails during image streaming - Dell Baremetal Deployment

[Mohankk85]

Hi,

We are trying to deploy EKS-A version 0.23 and k8s version 1.32 in Dell BareMetal server (Dell PowerEdge r750xs). We have prepared the admin machine with all required pre-requisite including mirror registry configuration and image import.
Admin machine has internet and the cluster nodes does not have internet. Cluster deployment has progressed fine and booted hook OS and created the tink-worker but workflow getting failed due to dial tcp 127.0.0.1:80: connect : connection refused.

Note: We are running internal registry in Admin machine with port 5000

root@eks-sit-admin01:~/eks-sit05/generated# kubectl get workflows -A
NAMESPACE NAME TEMPLATE STATE CURRENT-ACTION TEMPLATE-RENDERING
eksa-system eks-sit05-thwqc eks-sit05-thwqc STATE_FAILED stream image to disk successful

root@eks-sit-admin01:~/eks-setup1# cat eksa-mgmt-cluster-tink.yaml
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: Cluster
metadata:
name: eks-sit05
spec:
clusterNetwork:
cniConfig:
cilium: {}
pods:
cidrBlocks:
- 10.128.0.0/14
services:
cidrBlocks:
- 172.30.0.0/16

Registry mirror configuration added here

registryMirrorConfiguration:
endpoint: 172.xx.x.20
port: "5000"
ociNamespaces:
- registry: "public.ecr.aws"
namespace: ""
- registry: "783794618700.dkr.ecr.us-west-2.amazonaws.com"
namespace: "eks-anywhere"
caCertContent: |
-----BEGIN CERTIFICATE-----
1jQRWWImNEBQCxBqeFoPhuoya3+MYaBPbKjo2h/R/5v61JffkJSu5pdIYEDCNrZt
MgPl/KAJVPW78Eay7Q==
-----END CERTIFICATE-----

controlPlaneConfiguration:
count: 1
endpoint:
host: "172.xx.x.63"
machineGroupRef:
kind: TinkerbellMachineConfig
name: eks-sit05-cp

datacenterRef:
kind: TinkerbellDatacenterConfig
name: eks-sit05

kubernetesVersion: "1.32"
managementCluster:
name: eks-sit05

workerNodeGroupConfigurations:

• count: 0
  machineGroupRef:
  kind: TinkerbellMachineConfig
  name: eks-sit05
  name: eks-sit05-wk

---

apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellDatacenterConfig
metadata:
name: eks-sit05
spec:
osImageURL: "http://172.xx.x.xx:8080/ubuntu-2204-kube-1-32.gz"
tinkerbellIP: "172.xx.x.xx"
hookImagesURLPath: "http://172.xx..x.xx:8080/hook"

---

apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellMachineConfig
metadata:
name: eks-sit05-cp
spec:
hardwareSelector:
type: master
osFamily: ubuntu
users:

• name: necadmin
  sshAuthorizedKeys:
  • ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDIbmrtrG3X3QB7xmQEpOPxyyACTTrAZDilkTWjkVlb2jlbVRNnVZ8wxcmL

---

apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellMachineConfig
metadata:
name: eks-sit05
spec:
hardwareSelector:
type: worker
osFamily: ubuntu
users:

• name: necadmin
  sshAuthorizedKeys:
  • ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDIbmrtrG3X3QB7xmQEpOPxyyACTTrAZDilkTWjkVlb2jlbVRNnVZ8wxcmL

---

apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: TinkerbellTemplateConfig
metadata:
creationTimestamp: null
name: eks-sit05
spec:
template:
global_timeout: 6000
id: ""
name: eks-sit05
tasks:
- actions:
- environment:
COMPRESSED: "true"
DEST_DISK: '{{ index .Hardware.Disks 0 }}'
IMG_URL: http://172.16.8.20:8080/ubuntu-2204-kube-1-32.gz
image: 172.xx.x.xx:5000/eks-anywhere/tinkerbell/hub/image2disk:d524b77c7a44525c4318da3d2b5857c03711f3f8-eks-a-101:8cc3ff579491
name: stream image to disk
timeout: 600
- environment:
DEST_DISK: '{{ formatPartition ( index .Hardware.Disks 0 ) 2 }}'
DEST_PATH: /etc/netplan/config.yaml
DIRMODE: "0755"
FS_TYPE: ext4
GID: "0"
MODE: "0644"
STATIC_NETPLAN: "true"
UID: "0"
image: 172.xx.x.xx:5000/eks-anywhere/tinkerbell/hub/writefile:d524b77c7a44525c4318da3d2b5857c03711f3f8-eks-a-101:e1d170923f09
name: write netplan config
pid: host
timeout: 90
- environment:
CONTENTS: 'network: {config: disabled}'
DEST_DISK: '{{ formatPartition ( index .Hardware.Disks 0 ) 2 }}'
DEST_PATH: /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
DIRMODE: "0700"
FS_TYPE: ext4
GID: "0"
MODE: "0600"
UID: "0"
image: 172.xx.x.xx:5000/eks-anywhere/tinkerbell/hub/writefile:d524b77c7a44525c4318da3d2b5857c03711f3f8-eks-a-101:e1d170923f09
name: disable cloud-init network capabilities
timeout: 90
- environment:
CONTENTS: |
datasource:
Ec2:
metadata_urls: [http://172.xx.xx.xx:50061,http://172.xx.x.xx:50061,http://172.xx.x.xx:50061]
strict_id: false
manage_etc_hosts: localhost
warnings:
dsid_missing_source: off
DEST_DISK: '{{ formatPartition ( index .Hardware.Disks 0 ) 2 }}'
DEST_PATH: /etc/cloud/cloud.cfg.d/10_tinkerbell.cfg
DIRMODE: "0700"
FS_TYPE: ext4
GID: "0"
MODE: "0600"
UID: "0"
image: 172.xx.x.xx:5000/eks-anywhere/tinkerbell/hub/writefile:d524b77c7a44525c4318da3d2b5857c03711f3f8-eks-a-101:e1d170923f09
name: add cloud-init config
timeout: 90
- environment:
CONTENTS: |
datasource: Ec2
DEST_DISK: '{{ formatPartition ( index .Hardware.Disks 0 ) 2 }}'
DEST_PATH: /etc/cloud/ds-identify.cfg
DIRMODE: "0700"
FS_TYPE: ext4
GID: "0"
MODE: "0600"
UID: "0"
image: 172.xx.x.xx:5000/eks-anywhere/tinkerbell/hub/writefile:d524b77c7a44525c4318da3d2b5857c03711f3f8-eks-a-101:e1d170923f09
name: add cloud-init ds config
timeout: 90
- image: 172.xx.x.xx:5000/eks-anywhere/tinkerbell/hub/reboot:d524b77c7a44525c4318da3d2b5857c03711f3f8-eks-a-101:588132d90844
name: reboot
pid: host
timeout: 90
volumes:
- /worker:/worker
name: eks-sit05
volumes:
- /dev:/dev
- /dev/console:/dev/console
- /lib/firmware:/lib/firmware:ro
worker: '{{.device_1}}'
version: "0.1"
status: {}

support-bundle-2026-01-12T09_05_14.tar.gz