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
kuadrant-operator seems to delete any cert-manager Certificate resource that it's not directly managed by Kuadrant. Even without a TLSPolicy in place, each time the kuadrant-operator-controller-manager pod starts, it wipes out any Certificate resources in any namespace.
Logs (debug mode) show the Certificate deletion event, but not the actual deletion operation itself:
Have cert-manager installed in the cluster, with some Certificate resources in place
Install kuadrant-operator, a Kuadrant resource and a Gateway
Check that as soon as the kuadrant-operator starts, it picks up the Certificates that already exist in the cluster. Then, those Certificates are deleted, I'm assuming that by the kuadrant-operator-controller-manager pod itself. Behavior can be forces by just deleting the pod and letting it start a again.
Expected behavior
Any Certificate resource that is not directly managed by Kuadrant should be left intact.
Additional context
Pasting the topology here. Note that this is still a work in progress and there are not Kuadrant policies yet, nor there are any HTTPRoutes attached to the Gateway yet.
Describe the bug
kuadrant-operator seems to delete any cert-manager Certificate resource that it's not directly managed by Kuadrant. Even without a TLSPolicy in place, each time the kuadrant-operator-controller-manager pod starts, it wipes out any Certificate resources in any namespace.
Logs (debug mode) show the Certificate deletion event, but not the actual deletion operation itself:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Any Certificate resource that is not directly managed by Kuadrant should be left intact.
Additional context
Pasting the topology here. Note that this is still a work in progress and there are not Kuadrant policies yet, nor there are any HTTPRoutes attached to the Gateway yet.
The text was updated successfully, but these errors were encountered: