Describe the bug
The KrakenD container does not trust self signed certs like the dotnet cli dev certs used by a .NET Aspire application. In attempting to build a component I would expect to be able to use the config allow_insecure_connections to publish to an OTEL OTLP Endpoint. However, I can only get this to work on http. Given KrakenD is acting as a client here shouldn't it be able in development to ignore the OTLP endpoint cert? Please note this is in using the GRPC protocol for communicating with the OTEL OTLP Endpoint.
The equivalent of this command was ran by .NET Aspire:
`docker run --rm -it -v $PWD:/etc/krakend \
-e FC_ENABLE=1 \
-e FC_OUT=result.json \
-e KRAKEND_ALLOW_INSECURE_CONNECTIONS=true \
devopsfaith/krakend:2.7.0 \
run -c /etc/krakend/config/krakend.json -d`
Expected behavior
KrakenD to publish metrics and traces to the local OTLP endpoint provided by .NET Aspire.
Environment info:
Describe the bug The KrakenD container does not trust self signed certs like the dotnet cli dev certs used by a .NET Aspire application. In attempting to build a component I would expect to be able to use the config
allow_insecure_connections
to publish to an OTEL OTLP Endpoint. However, I can only get this to work onhttp
. Given KrakenD is acting as a client here shouldn't it be able in development to ignore the OTLP endpoint cert? Please note this is in using the GRPC protocol for communicating with the OTEL OTLP Endpoint.Your configuration file:
Commands used How did you start the software?
Expected behavior KrakenD to publish metrics and traces to the local OTLP endpoint provided by .NET Aspire.
Logs