SpiderUnderUrBed @ SpiderUnderUrBed @lemmy.zip Posts 9Comments 8Joined 2 mo. ago
I'm all for pettyness in most cases.. but uhh. This is a bit much don't ya think?
I feel like github should have verified repositories
How did they get the rope around him lol
Nevermind, fixed, this is what I tried applying, or maybe i should have waited for a bit and it might of worked, regardless, just incase its useful to anyone:
apiVersion: v1
kind: ConfigMap
metadata:
name: coredns
namespace: kube-system
data:
Corefile: |
.:53 {
errors
health
ready
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
fallthrough in-addr.arpa ip6.arpa
}
hosts /etc/coredns/NodeHosts {
ttl 60
reload 15s
fallthrough
}
prometheus :9153
forward . 1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4
cache 30
loop
reload
loadbalance
}
The issue is solved now, thanks
Ok so, I think it was running on the wrong node and using thats resolv.conf which I did not update, but I am getting a new issue:
2025-05-02T21:42:30Z INF Starting tunnel tunnelID=72c14e86-612a-46a7-a80f-14cfac1f0764 2025-05-02T21:42:30Z INF Version 2025.4.2 (Checksum b1ac33cda3705e8bac2c627dfd95070cb6811024e7263d4a554060d3d8561b33) 2025-05-02T21:42:30Z INF GOOS: linux, GOVersion: go1.22.5-devel-cf, GoArch: arm64 2025-05-02T21:42:30Z INF Settings: map[no-autoupdate:true] 2025-05-02T21:42:30Z INF Environmental variables map[TUNNEL_TOKEN:*****] 2025-05-02T21:42:30Z INF Generated Connector ID: 7679bafd-f44f-41de-ab1e-96f90aa9cc34 2025-05-02T21:42:40Z ERR Failed to fetch features, default to disable error="lookup cfd-features.argotunnel.com on 10.90.0.10:53: dial udp 10.90.0.10:53: i/o timeout" 2025-05-02T21:43:30Z WRN Unable to lookup protocol percentage. 2025-05-02T21:43:30Z INF Initial protocol quic 2025-05-02T21:43:30Z INF ICMP proxy will use 10.60.0.194 as source for IPv4 2025-05-02T21:43:30Z INF ICMP proxy will use fe80::eca8:3eff:fef1:c964 in zone eth0 as source for IPv6
2025-05-02T21:42:40Z ERR Failed to fetch features, default to disable error="lookup cfd-features.argotunnel.com on 10.90.0.10:53: dial udp 10.90.0.10:53: i/o timeout"
kube-dns usually isnt supposed to give a i/o timeout when going to external domains, im pretty sure its supposed to forward it to another dns server, or do i have to configure that?
Is it possible to set what DNS server cloudflare tunnels uses when resolving local ips?
??? He said he talked to the principal multiple times
I solved the issue, the jellyfin pod for some reason was connecting to the wrong endpoint for the internal kube-dns service, I fixed that, and also made it use the internal pods FQDN and it works.
It does not work, as long as it goes to a cloudflare domain, the is a io timeout because of some DNS issue, any other suggestions?