Details
-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
False
-
None
-
False
-
NEW
-
NEW
-
Before this update, the tls.insecureSkipVerify field of an output could not be set to true without a secret defined. With this update, a secret is no longer required to set this parameter.
-
Bug Fix
-
Log Collection - Sprint 248
Description
Description of problem:
User's should be able to define tls.insecureSkipVerify=false even when the define no secret. This logic exists only for Loki but is relevent for any output that supports TLS
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- ...
