-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
COO should have a controller watching the cluster's API server TLS configuration. When it changes, it should either exit or reconcile all managed resources. It should also be able to convert the cluster TLS configuration into a Go TLS configuration.
https://github.com/openshift/controller-runtime-common might become useful (it should get ideas such as https://github.com/openshift/library-go/pull/2082).
- blocks
-
COO-1553 Apply cluster TLS profile configuration to monitoring UIPlugin components
-
- To Do
-
-
COO-1554 Apply cluster TLS profile configuration to logging UIPlugin components
-
- To Do
-
-
COO-1555 Apply cluster TLS profile configuration to Perses components
-
- To Do
-
-
COO-1558 Apply cluster TLS profile configuration to dashboard UIPlugin components
-
- To Do
-
-
COO-1549 Apply cluster TLS profile configuration to the Prometheus operator webhook service
-
- To Do
-
-
COO-1550 Apply cluster TLS profile configuration to cluster health analyzer components
-
- To Do
-
-
COO-1552 Apply cluster TLS profile configuration to tracing UIPlugin components
-
- To Do
-
-
COO-1556 Apply cluster TLS profile configuration to Prometheus operator
-
- To Do
-
-
COO-1557 Apply cluster TLS profile configuration to COO
-
- To Do
-
-
COO-1551 Apply cluster TLS profile configuration to signal correlation components
-
- On QA
-