-
Story
-
Resolution: Done
-
Normal
-
None
-
3
-
False
-
False
-
Undefined
-
-
Logging (Core) - Sprint 200, Logging (Core) - Sprint 201, Logging (Core) - Sprint 204, Logging (Core) - Sprint 205
Story
As a user of Cluster Log Forwarding,
I want to rely upon username and password to authenticate against an external Elasticsearch instance.
Acceptance Criteria
- Username and passwords are not visible in the configuration as plain text but configured as a Secret
- Integration test that utilizes username and password for the Elasticsearch output
- Username and password is not supported for OpenShift Logging managed Elasticsearch store
- Must work with either HTTP or HTTPs.
Notes
- Modify verification checks to require username and password as a set
Documentation Consideration
- Extend the forwarding to Elasticsearch section with information on how to setup a Secret that contains username and password, and if necessary everything for setting up certificates if HTTPS is being used.
- is blocked by
-
LOG-1372 CLO always set some incorrect default values in fluent.conf when forward log to external elasticsearch with secret
- Closed
- is documented by
-
RHDEVDOCS-3002 Enable username and password for the Elasticsearch output type
- Closed
- relates to
-
LOG-1652 The fluentd doesn't use the new username/password after changing username/password in the pipeline secret.
- Closed
- links to
(7 links to)