While running mononoke in the cluster has a number of advantages, particularly when combined with a dynamic source of images, like kpack. It should also be possible to run offline against a yaml file via a CLI, although any opinions that need knowledge of the cluster would need to be disabled. This could provide a more natural fit with organizations that want a GitOps flow to review monnonoke's opinions before going live.
We'd likely need to offer basic filters for namespace, name/selector, kind, apiGroup and container name to limit the resources that are managed in multi-document files.
While running mononoke in the cluster has a number of advantages, particularly when combined with a dynamic source of images, like kpack. It should also be possible to run offline against a yaml file via a CLI, although any opinions that need knowledge of the cluster would need to be disabled. This could provide a more natural fit with organizations that want a GitOps flow to review monnonoke's opinions before going live.
We'd likely need to offer basic filters for namespace, name/selector, kind, apiGroup and container name to limit the resources that are managed in multi-document files.