-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.16
-
None
-
None
-
False
-
-
-
Enhancement
-
In Progress
It is implementation of the solution 1 from the document https://docs.google.com/document/d/1r3sC_7ZU7qkxvafpEkAJKMTmtcWAwGOI6W_SZGkvP6s/edit#heading=h.kfjcs2uvui3g
We need to, base on the ykarel@redhat.com's patch make proper integration of our CRs with the insights-operator. It needs to collect data from the 'OpenstackControlPlane', 'OpenstackDataPlaneDeployment' and 'OpenstackDataPlaneNodeSet' CRs with proper anonymization of the data like IP addresses etc. It also needs to set somehow "good" ID to identify Openstack cluster as we cannot rely on the Openshitf clusterID because we may have more than one Openstack cluster on the same OCP cluster.
To identify openstack cluster maybe uuid of the OpenstackControlPlane CR can be used. If no we will need to figure out something else there.
Definition of done:
- insights-operator knows about Openstack related CRs, can collect data from it, anonymize that data and send to the insights-server,
- it can collect data from CRs from more than one Openstack cluster and send them separately to the insights servereh
- clones
-
OSPRH-5904 Integrate openstack related CRs with insights-operator
- Closed
- is triggered by
-
OSPRH-4003 Evaluate how to ingest data into Insights
- Closed
- links to
-
RHSA-2024:6824 OpenShift Container Platform 4.16.z security update