-
Spike
-
Resolution: Done
-
Critical
-
None
-
None
-
5
-
False
-
-
False
-
rhos-conplat-observability
-
-
-
CloudOps 2025 Sprint 19
-
1
-
Important
Summary:
- Determine if CloudKitty can use TLS authentication in the way that is implemented in Loki (storage domain). Does not need to be automated, but we need to determine if a certificate chain can be manually generated and utilized by CloudKitty.
Goal:
- Determine if we can use TLS authentication to access Loki with CloudKitty as designed, or if we need to determine a non-authentication path to accessing the storage domain.
TimeBox:
- 2-3 days
Deliverables/Outcomes:
- Determine if TLS authentication (deployed manually) can be achieved.
- If that is not possible, document why (so that we can implement that in the future within the GA timeframe) and identify if there is an alternative.
- If there is no alternative and we must use a non-authenticated connection, work with PM and PO along with the Loki team to investigate how we can make this happen with production images.
- depends on
-
OSPRH-19446 Deploy an OpenShift environment using 4.18 and OpenShift Logging for investigation of TLS connections to Loki
-
- Closed
-