Abhinav Pandey
Abhinav Pandey
Does appending the ":443" port cause any issues with pushing the images?
> > Does appending the ":443" port cause any issues with pushing the images? > > A certain customer registry rejects the push request. They manually tested the push after...
Can you confirm if your other control and worker nodes were provisioned successfully and it just only the GPU node/s that are stuck in that stage? Another thing to mention...
Bumping up the priority on this one as it's pretty important issue that has come up multiple times especially for cleaning up local bootstrap cluster and the cluster-name folder.
For anyone who lands on this issue, EKS Anywhere currently supports [proxy configuration](https://anywhere.eks.amazonaws.com/docs/reference/clusterspec/optional/proxy/) as well as [local registry configuration](https://anywhere.eks.amazonaws.com/docs/reference/clusterspec/optional/registrymirror/) that will allow users to create clusters in disconnected environments.
If you provide a `TinkerbellTemplateConfig` for a machine, it will override the default template. If you want to use this custom config, you will need to add the stream-image action,...
Marking this issue was `wontfix` for now but will leave it open to track interest
This is for an internal dependency of Tinkerbell stack that is used for creating bare-metal clusters. We did decide to stick with kube-vip actually so ignore this issue