ZappaBoy commented on issue #10505:
URL: https://github.com/apache/apisix/issues/10505#issuecomment-2144764295
> @shreemaan-abhishek, it seems like issue is not connected with
`apisix.yaml` config changing (as described in #10530), we are facing same
issue at initial startup (without chaning apisix.yaml) in docker environment.
We have the following apisix.yaml configuration:
>
> ```yaml
> upstreams:
> -
> id: some_service_upstream
> nodes:
> "${{SOME_SERVICE_UPSTREAM_ADDRESS}}": 1
> type: roundrobin
> ```
>
> and docker-compose file:
>
> ```yaml
> version: "3"
>
> services:
> apisix:
> build:
> context: ../../gateway
> dockerfile: ../docker/Dockerfile.public-api-gateway
> container_name: apisix_api_gateway
> restart: always
> environment:
> # Upstream Addresses Envs Start
> LOS_SERVICE_UPSTREAM_ADDRESS: ${LOS_SERVICE_UPSTREAM_ADDRESS}
> ports:
> - "9180:9180/tcp"
> - "9080:9080/tcp"
> - "9091:9091/tcp"
> - "9444:9443/tcp"
> - "9092:9092/tcp"
> networks:
> apisix:
>
> networks:
> apisix:
> driver: bridge
> ```
>
> while doing requests to LOS service we are seeing this in console:
>
>
>
> but request is hitting upstream service.
@ilya-tishonok The same issue here. I also tried with different `apisix`
versions, specifying `dns_resolver` property and changing `apisix.yaml`
settings but the issue still appears. The services return the responses
correctly and the responses are also cached by the `proxy-cache` plugin but the
`parse_domain_for_nodes()` function always gives the same error.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
