openshift/cluster-logging-operator

Procedure to sign the certificates

RudraprakashR opened this issue · 5 comments

RudraprakashR commented

Bug Description
The CA which comes as part of elasticsearch provided by openshift is made use by the fluentd to make a connection to the Elasticsearch.
The certificate used by fluentd i.e., tls.crt and private tls.key are signed by using the same CA as used by openshift elastic search
If we are trying to use a custom fluentd with the same tls.crt and tls.key of Openshift provided fluentd - connection is possible.
What is the procedure to sign the custom fluentd using the same CA as used by openshift elastic search to connect to it ?

Environment

  • OKD 4.7
  • ClusterLogging instance - 5.0.7-27

Expected behavior
Custom fluentd to connect to Openshift elasticsearch and write the logs.

Actual behavior
Custom fluentd not able to connect to Openshift elasticsearch and write the logs.

RudraprakashR commented

Can I please get to know the procedure to sign the custom fluentd using the same CA as used by openshift elastic search to connect to it ?

openshift-bot commented

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

openshift-bot commented

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci commented

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.