You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I'm not sure if the loki-Team see this as a bug or feature I think a Feature Request is a good start point for a discussion.
Is your feature request related to a problem? Please describe.
There are some Setups out there which intercepts the https connection via a HTTP-Proxy and re-encrypt the traffic.
It would be nice to add an option to add a Trusted-CA Bundle from a file location or ENV Var.
As I have seen that the current proxy library have not such a feature have I add a Issue Feature Request: Add Custom CA for TLS intercepting proxy (mitm Proxy)
Describe the solution you'd like
We would like to be able to add a file location or a ENV Var to the Deployment/Pod/Setup where a custom Trusted CA is located so that loki components can use this CA Bundle to interact with a Proxy.
Describe alternatives you've considered
We have now created a direct connection for the azure blob storage, because of that is the ingester now able to write logs to azure blob storage.
The text was updated successfully, but these errors were encountered:
As I'm not sure if the loki-Team see this as a bug or feature I think a Feature Request is a good start point for a discussion.
Is your feature request related to a problem? Please describe.
There are some Setups out there which intercepts the https connection via a HTTP-Proxy and re-encrypt the traffic.
It would be nice to add an option to add a Trusted-CA Bundle from a file location or ENV Var.
As I have seen that the current proxy library have not such a feature have I add a Issue Feature Request: Add Custom CA for TLS intercepting proxy (mitm Proxy)
This is the code to which I refer to.
loki/pkg/storage/chunk/client/azure/blob_storage_client.go
Line 66 in 0dc9d67
Describe the solution you'd like
We would like to be able to add a file location or a ENV Var to the Deployment/Pod/Setup where a custom Trusted CA is located so that loki components can use this CA Bundle to interact with a Proxy.
I see there some possible solutions.
Describe alternatives you've considered
We have now created a direct connection for the azure blob storage, because of that is the ingester now able to write logs to azure blob storage.
The text was updated successfully, but these errors were encountered: