Re: Mysql operator on_secret_create
Hi,
yes, the operator reacts on all secret creation events in all namespaces, no matter if there is a cluster in the specific namespace or not. Once the handler is fired it checks for clusters in the namespace where the secret is created and if there is none just finishes.
How do you spot the memory increase?
Using the declarative way of Kopf there is no way (up to my knowledge) how to install a handler that reacts on a secret with a name which is not known when the operator is created. Maybe if the kopf.on.create() (the decorator) is called from the operator code when a cluster is created and the secret names are known. This needs exploration.
In any case, kopf listens to all events in the K8s cluster, no matter if there is a handler installed or not.
Subject
Written By
Posted
Re: Mysql operator on_secret_create
June 10, 2022 07:31AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.