Amit Kumar Das

We can try below metacontrollers to prove if Metac supports this usecase: - DecoratorController - GenericController

These are some of the current ways of testing kubernetes controllers: - https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests.md - https://kubernetes.io/blog/2019/03/22/kubernetes-end-to-end-testing-for-everyone/

@grzesuav the second option. This is all about using metac as a conformance controller. We might use any language. However rego or jsonnet should also do this job. It should...

`Assert` results will most probably be set as status & conditions against the watched resource. So users need to define their custom resource which has status & conditions & so...

I guess this can be tied with https://github.com/AmitKumarDas/metac/issues/65 to solve both

This PR (https://github.com/AmitKumarDas/metac/pull/60) was committed recently to handle updating attachment resources even if these are pending deletion. However, it will be better to have this tunable declared in the specs...

cc @grzesuav

klog should be drop in replacement. Integration tests have them already. I would vote for klog. As per this [example](https://github.com/kubernetes/klog/blob/master/examples/klogr/main.go), it has all the fields needed to output in a...

As discussed, Integration Tests in metac was using klog. This [PR](https://github.com/AmitKumarDas/metac/pull/138) makes use of klog with appropriate flags.

Sounds great @grzesuav