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
Link the lifecycle of the kuadrant operator with the topology configmap. Currently, when the operator starts, it will create and maintain the topology configmap in the namespace where the operator is deployed. It is missing the implementation of the removal of the topology configmap when the operator is deleted.
Note: The ConsolePlugin resource, together with the associated deployment and service, follows the life events of the topology configmap. When the topology is created, so it is the ConsolePlugin (on openshift). Whereas when the topology is deleted, so it is the ConsolePlugin and associated resources. The ConsolePlugin was introduced in #884
The text was updated successfully, but these errors were encountered:
Link the lifecycle of the kuadrant operator with the
topology
configmap. Currently, when the operator starts, it will create and maintain thetopology
configmap in the namespace where the operator is deployed. It is missing the implementation of the removal of thetopology
configmap when the operator is deleted.The text was updated successfully, but these errors were encountered: