Add demo templates to the constraint template library

[maxsmythe]

Signed-off-by: Max Smythe smythe@google.com

[ritazh]

nit: To be consistent with stuff already in library/pod-security-policy, for example this, can you pls also add example.yaml for each one of these?

[maxsmythe]

Done.

Note I think the library directory structure may need to change for the permanent repo. There are a few problems.

It's not clear who this library is intended for, admins or constraint developers. This is a problem in itself, but there are problems with the structure as-is depending on the audience.

If admins:

• The templates should not all be called template.yaml, that makes it hard to copy templates into a new place
• Templates should live in a separate directory tree from constraint.yaml and example.yaml so that I can kubectl apply -f at some root and apply all templates in the library. It also makes it easier to batch copy templates to a different repo.

If constraint developers:

• We do not care about the resultant template, we want to generate them on the fly so we can build, test, repeat. We instead want a template template (golang template of a ConstraintTemplate, or similar)

[ritazh]

LGTM

[ritazh]

Regarding the library directory structure, let's discuss this as a group to get more feedback.

[maxsmythe]

LMK if you want to merge this before or after the directory update.

[ritazh]

Per our group discussion, maybe rename the folder library/demo to something else e.g. container, service, or just general, since we also have a demo folder outside of library that should be used for demo purposes. WDYT?

[maxsmythe]

SGTM, renaming to general and merging