It would rely on labels being present but also exclude the necessary resources.
What makes this plugin unique is that it should only run post-deployment. We can rely on something like metadata.uid to know that it runs in a cluster (better options are likely possible).
Remarks
Usage is not so nice to need a file to enable a plugin that runs on a cluster from anywhere.
The goal is to identify kubernetes resources which are not managed by GitOps.
Usage
Afterwards:
Implementation details
metadata.uid
to know that it runs in a cluster (better options are likely possible).Remarks
Usage is not so nice to need a file to enable a plugin that runs on a cluster from anywhere.
Dependencies