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
Instead of manually configuring the creation-time patch webhook, the patch-operator controller could provide a CreationTimePatch CRD and a controller, which watches those CRs and configures the webhook accordingly.
I would suggest to support multiple CreationTimePatchConfiguration CRs, which are then consolidated into a single webhook configuration, but having a singleton CRD is also okay.
Multiple CRs would support the use-case were I can configure a new CRD created by some operator installed in the same GitOps subproject/subdir which installed the other operator and don't have to modify another place to support that. But this may be an advanced use-case and not sure how easy it is to map multiple CRs to one resource in the end.
The text was updated successfully, but these errors were encountered:
Instead of manually configuring the creation-time patch webhook, the patch-operator controller could provide a
CreationTimePatch
CRD and a controller, which watches those CRs and configures the webhook accordingly.I would suggest to support multiple CreationTimePatchConfiguration CRs, which are then consolidated into a single webhook configuration, but having a singleton CRD is also okay.
Multiple CRs would support the use-case were I can configure a new CRD created by some operator installed in the same GitOps subproject/subdir which installed the other operator and don't have to modify another place to support that. But this may be an advanced use-case and not sure how easy it is to map multiple CRs to one resource in the end.
The text was updated successfully, but these errors were encountered: