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
Now that catalogd and operator-controller share the same namespace, deployment of operator-controller should properly handle this redundancy and ensure that the version of the olmv1-system namespace from operator-controller is the one that ends up on the cluster.
@joelanford brought up the question of whether this signals that we should consider combining catalogd and operator-controller into a monorepo, especially as the two continue to become more tightly coupled.
Here's the PR for the TLS work that lead to this question.
The text was updated successfully, but these errors were encountered:
Now that catalogd and operator-controller share the same namespace, deployment of operator-controller should properly handle this redundancy and ensure that the version of the olmv1-system namespace from operator-controller is the one that ends up on the cluster.
@joelanford brought up the question of whether this signals that we should consider combining catalogd and operator-controller into a monorepo, especially as the two continue to become more tightly coupled.
Here's the PR for the TLS work that lead to this question.
The text was updated successfully, but these errors were encountered: