Containerd or cri proxy settings #7909
Replies: 1 comment 3 replies
-
Did you set https proxy in talos environment as at the bottom of
https://www.talos.dev/v1.5/reference/kernel/ ?
…On Sat, Oct 28, 2023 at 5:15 AM eneko-perez ***@***.***> wrote:
Hi all,
I'm trying to setup Talos behind a proxy and in the bootstrapping process
I can't download any image (kubelet, etcd) so the installation can not
continue and I'm in a booting permanent state. The errors I see in the logs
are:
[ 63.900389] [talos] retrying error: failed to pull image "
ghcr.io/siderolabs/kubelet:v1.28.2": failed to resolve reference "
ghcr.io/siderolabs/kubelet:v1.28.2": failed to do request: Head "
https://ghcr.io/v2/siderolabs/kubelet/manifests/v1.28.2": proxyconnect
tcp: dial tcp: lookup (my proxy info here) on 10.96.64.9:53: read udp
10.96.105.3:44231->10.96.64.9:53: i/o timeout
The rest of the installation has gone well so far by defining env
variables in the control plane yaml.
I tried to append this information to containerd this way:
- content: | [Service] Environment="HTTPS_PROXY=myproxyaddress:port" path:
/etc/cri/conf.d/20-customization.part op: append
but I'm not sure if it's working or not or I'm doing something wrong.
Besides this error, I'm getting a lot of:
[ 3479.026763] [talos] controller failed {"component":
"controller-runtime", "controller": "k8s.NodeApplyController", "error": "1
error(s) occurred:\n\terror getting node: Get \"
https://localhost:6443/api/v1/nodes/talos-08x-6in?timeout=30s\": dial tcp
[::1]:6443: connect: connection refused"} [ 3482.797366] [talos] task
startAllServices (1/1): service "kubelet" to be "up" [ 3484.515127] [talos]
hello failed {"component": "controller-runtime", "controller":
"cluster.DiscoveryServiceController", "error": "rpc error: code =
Unavailable desc = connection error: desc = \"transport: Error while
dialing: dial tcp: lookup discovery.talos.dev on 10.96.64.9:53: read udp
10.96.105.3:38563->10.96.64.9:53: i/o timeout\"", "endpoint": "
discovery.talos.dev:443"}
Any suggestions to fix these two issues? It feels like I'm almost there
but it's incredible the amount of time I'm dedicating to such a simple
setup, in part due to my lack of understanding of how Talos works
internally but also because of my entangled setup.
Thank you.
—
Reply to this email directly, view it on GitHub
<#7909>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQGWG5KODW7JR4VVSS7WNS3YBTZNFAVCNFSM6AAAAAA6UBO4M6VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZVG44DMOBSGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
I'm trying to setup Talos behind a proxy and in the bootstrapping process I can't download any image (kubelet, etcd) so the installation can not continue and I'm in a booting permanent state. The errors I see in the logs are:
[ 63.900389] [talos] retrying error: failed to pull image "ghcr.io/siderolabs/kubelet:v1.28.2": failed to resolve reference "ghcr.io/siderolabs/kubelet:v1.28.2": failed to do request: Head "https://ghcr.io/v2/siderolabs/kubelet/manifests/v1.28.2": proxyconnect tcp: dial tcp: lookup (my proxy info here) on 10.96.64.9:53: read udp 10.96.105.3:44231->10.96.64.9:53: i/o timeout
The rest of the installation has gone well so far by defining env variables in the control plane yaml.
I tried to append this information to containerd this way:
- content: | [Service] Environment="HTTPS_PROXY=myproxyaddress:port" path: /etc/cri/conf.d/20-customization.part op: append
but I'm not sure if it's working or not or I'm doing something wrong.
Besides this error, I'm getting a lot of:
[ 3479.026763] [talos] controller failed {"component": "controller-runtime", "controller": "k8s.NodeApplyController", "error": "1 error(s) occurred:\n\terror getting node: Get \"https://localhost:6443/api/v1/nodes/talos-08x-6in?timeout=30s\": dial tcp [::1]:6443: connect: connection refused"} [ 3482.797366] [talos] task startAllServices (1/1): service "kubelet" to be "up" [ 3484.515127] [talos] hello failed {"component": "controller-runtime", "controller": "cluster.DiscoveryServiceController", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp: lookup discovery.talos.dev on 10.96.64.9:53: read udp 10.96.105.3:38563->10.96.64.9:53: i/o timeout\"", "endpoint": "discovery.talos.dev:443"}
Any suggestions to fix these two issues? It feels like I'm almost there but it's incredible the amount of time I'm dedicating to such a simple setup, in part due to my lack of understanding of how Talos works internally but also because of my entangled setup.
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions