Ah!
I have been struggling with this exact issue all day. I am using the rancher docker containers though. I have tried with both 0.8.0 and 0.9.0 versions of the kong-ingress-controller in conjunction with kong 1.5.0. This is the first time i have had this issue, and we have about 6 other clusters, so i assumed it was something with my environment - likely dns, possibly the ubuntu.
Do you have any further insight into this issue @giniz? I am pretty well confused. I am using ubuntu 18.04.
I also made another deployment with two containers in a single pod to test out just a simple curl of http://localhost and ensure that one container can access the other container in a single pod. This worked fine as expected, so i think my cluster is sane.
I also ran wget --no-check-certificate https://localhost:8444/ inside the proxy container and got a good response, so the admin api is operating as expected.
The code in the ingress controller is just grabbing the root api object.
// Root returns the response of GET request on root of
// Admin API (GET /).
func (c *Client) Root(ctx context.Context) (map[string]interface{}, error) {
req, err := c.NewRequest("GET", "/", nil, nil)
if err != nil {
return nil, err
}
var root map[string]interface{}
_, err = c.Do(ctx, req, &root)
if err != nil {
return nil, err
}
return root, nil
}
I am running out of ideas… I will probably modify and build the ingress-controller and re-deploy and see if i can’t learn anything.