Hi colleagues!
We have been running discovery against our openshift environment, and we see for [cmdb_ci_oslv_container] all CIs have install_status set to Installed, while the [cmdb_ci_oslv_container] items show a correct kubernetes status (running/failed/succeeded).
We realize we are missing a retirement strategy, otherwise containers in install status accumulate over time,
and since they remain represented as CIs, the container count only grows.
Is there any best practice to implement a life cycle to retire succeeded or failed containers which are no longer running?
We've searched around but found nothing, if anyone could provide some experience it will be much appreciated, so we can implement a robust standard solution for these ephemeral workloads.
(We are still using the legacy install_status).
Thanks!
