You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
The YAMLs for the events operator contain CRDs. These are cluster-scoped resources that we do not want to destroy when a Team CR instance is deleted, since they may be used by other Team CR instances.
We should find a way for the Config controller to apply these CRDs. Or perhaps include them in the CSV for the kabanero operator? I think I am OK with either approach. If the config controller applies them, they can be removed when the Config CR instance is removed. In the CSV, the lifecycle would be controller by OLM.
The text was updated successfully, but these errors were encountered:
The YAMLs for the events operator contain CRDs. These are cluster-scoped resources that we do not want to destroy when a Team CR instance is deleted, since they may be used by other Team CR instances.
We should find a way for the Config controller to apply these CRDs. Or perhaps include them in the CSV for the kabanero operator? I think I am OK with either approach. If the config controller applies them, they can be removed when the Config CR instance is removed. In the CSV, the lifecycle would be controller by OLM.
The text was updated successfully, but these errors were encountered: