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
I am doing a feasibility around implementing a cert-manager.io operator using KubeOps. In the cert-manager.io concept, certificate approvals are given via updating status.conditions field which does not update generation. Therefore, my .NET reconciler is never called. Instead, I get this message
Entity "CertificateRequest/test-cert-1" modification did not modify generation. Skip event.
I would like to react on this status change in my controller, but looking at the KubeOps code, it does not seem to be possible.
To my knowledge, not calling the reconciler when the generation has not changed is not a usual requirement, although it can make sense most of the times.
To reproduce
Create a CRD and a controller
Update a resource's status
Reconciler is not called
Expected behavior
The reconciler is either always called, or there is an option to be informed even when the generation has not changed.
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I am doing a feasibility around implementing a cert-manager.io operator using KubeOps. In the cert-manager.io concept, certificate approvals are given via updating status.conditions field which does not update generation. Therefore, my .NET reconciler is never called. Instead, I get this message
I would like to react on this status change in my controller, but looking at the KubeOps code, it does not seem to be possible.
To my knowledge, not calling the reconciler when the generation has not changed is not a usual requirement, although it can make sense most of the times.
To reproduce
Expected behavior
The reconciler is either always called, or there is an option to be informed even when the generation has not changed.
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: