Skip to content

bug: for some reason dns resolving doesnt work in pods after fresh install  #64

Open
@metacoma

Description

@metacoma

it's affect neo4j deployment

$ kubectl -n context-purple logs purple-neo4j-0 -c install-apoc-plugin                   
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                              
                                 Dload  Upload   Total   Spent    Left  Speed                                                
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: github.com   
Warning: Problem : timeout. Will retry in 1 seconds. 3 retries left.                                                         
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: github.com   
Warning: Problem : timeout. Will retry in 2 seconds. 2 retries left.                                                         
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: github.com   
Warning: Problem : timeout. Will retry in 4 seconds. 1 retries left.                             

some additional diagnostic from the nicolaka/netshoot pod

tmp-shell  ~  ping github.com
ping: github.com: Name has no usable address

 tmp-shell  ~  cat /etc/resolv.conf
nameserver 10.43.0.10
search default.svc.cluster.local svc.cluster.local cluster.local 
options ndots:5

tmp-shell  ~  host github.com 10.43.0.10
Using domain server:
Name: 10.43.0.10
Address: 10.43.0.10#53
Aliases: 

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions