Kustomise files for daily

[idlewis]

start to deal with #177

[leochr]

@idlewis Thanks. Looks good. Just want to confirm the purpose of all-namespaces2. Is it to specify a different namespace? Wondering whether changing namespace: default in all-namespaces/kustomization.yaml would achieve the same

[idlewis]

@leochr Yes, the purpose of the all-namespaces2 is to specify a different a namespace, and yes this could be done in all-namespaces. However, the idea was that, because all-namespaces adds in a new resource file (the cluster roles yaml) I was expecting that users would want to treat all-namespaces as a base to build on, and probably would prefer to leave it untouched, rather than having to edit it. So all-namespaces2 is an example of how a user could build on all-namespaces without having to modify it.
If you think it is better to combine the two, I'm happy to do that.
I also will add a readme to explain it either way, once you are happy with the content.

[leochr]

Thanks @idlewis . It'll be good to separate the folders that customers should modify from the folders/files we provide (i.e. move all-namespace2 and test-namespace under examples)

Suggest the following names for the folders:
watch-own-namespace
watch-another-namespace
watch-all-namespaces

[leochr]

@idlewis Thanks for the update. If possible, it'll be good to have the examples directly under daily folder. This way that's the only folder customers would have to edit and also avoid accidentally modifying other folders directly under overlays.

Maybe you are planning to add, it'll be good to have an example for watch-another-namespace.

[idlewis]

@leochr I think I've addressed all the review comments. Hopefully should be ready for review/merge.

[leochr]

@idlewis Looks good. Thanks.