Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-1923

Refactor CLO to request certificates from EO instead of creating them

    XMLWordPrintable

Details

    • 3
    • False
    • False
    • NEW
    • VERIFIED
    • Logging (Core) - Sprint 210, Logging (Core) - Sprint 211, Logging (Core) - Sprint 212, Logging (Core) - Sprint 213

    Description

      Summary

      As a developer of CLO,
      I want certificates for the collector to be provided by EO when creating default storage,
      so the CLO no longer creates the certificates the EO needs for the ES cluster

      Acceptance Criteria

      • Verify deployment of greenfield CL with managed storage
      • Verify upgrades of existing CL with managed storage
      • Verify visualization of logs via Kibana

      Notes

      • Checkout hack/cr.yaml in EO's repo for the correct annotation to enable it.
      • Remove cert generation from CLO

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. LOG-2093 EO Self-generated certificates issue with Kibana when "logging.openshift.io/elasticsearch-cert-management: true" annotation is used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. LOG-2110 [release-5.3] EO Self-generated certificates issue with Kibana when "logging.openshift.io/elasticsearch-cert-management: true" annotation is used

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. LOG-2139 [release-5.3]Refactor CLO to request certificates from EO instead of creating them

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. LOG-4175 Code Cleanup for LOG-1923 - Certificate Handling in CLO

          • Undefined - Priority not specified.
          • Closed
          links to

          GitHub openshift/cluster-logging-operator#1265: WIP:LOG-1923: Refactor CLO to request certificates from EO instead of creating them

          GitHub openshift/cluster-logging-operator#2044: LOG-4175: code cleanup to remove the certificate handling modifications made for LOG-1923

          GitHub openshift/elasticsearch-operator#832: Align distinguished name (DN) of the certificate generated by EO with CLO

          GitHub openshift/origin-aggregated-logging#2233: LOG-1923:Fix username according to the subject in certificates

          GitHub openshift/origin-aggregated-logging#2235: Revert "LOG-1923:Fix username according to the subject in certificates"

          mentioned on

          GitLab Merge request - Updated US source to: 787ae81 Merge pull request #2044 from vparfonov/log4175

          Activity

            People

              vparfono Vitalii Parfonov
              jcantril@redhat.com Jeffrey Cantrill
              Qiaoling Tang Qiaoling Tang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: