Add nfd-worker-conf ConfigMap to deployment templates

[marquiz]

Add a virtually empty ConfigMap that is mounted inside the workers.
Makes it easier to start customizing the worker deployment e.g. with just:

$ kubectl -n ${NFD_NS} edit configmap nfd-worker-conf

Create a new 'templates' make target for inserting the content of
nfd-worker.conf.example into the configmap spec of the templates. Thus,
'make templates' should be run whenever the example config is update.
Update the verify.sh prow script to check that the templates are up to
date.

This patch also streamlines the documentation about configuration
management, reflecting the changes.

[ArangoGutierrez]

/assign

[ArangoGutierrez]

The operator does the same, an empty file, maybe we could, in the name of documentation, not do it via a virtual empty but a commented file (wish has the same effect) , and will help people

[ArangoGutierrez]

Suggested change

	nfd-worker.conf: |
	nfd-worker.conf: |
	#uncomment to configure
	#sources:
	# pci:
	# deviceClassWhitelist:
	# - "0200"
	# - "03"
	# - "12"
	# deviceLabelFields:
	# - "class"
	# - "vendor"
	# - "device"
	# - "subsystem_vendor"
	# - "subsystem_device"

[ArangoGutierrez]

Suggested change

	nfd-worker.conf: |
	nfd-worker.conf: |
	#uncomment to configure
	#sources:
	# pci:
	# deviceClassWhitelist:
	# - "0200"
	# - "03"
	# - "12"
	# deviceLabelFields:
	# - "class"
	# - "vendor"
	# - "device"
	# - "subsystem_vendor"
	# - "subsystem_device"

[ArangoGutierrez]

Suggested change

	nfd-worker.conf: |
	nfd-worker.conf: |
	#uncomment to configure
	#sources:
	# pci:
	# deviceClassWhitelist:
	# - "0200"
	# - "03"
	# - "12"
	# deviceLabelFields:
	# - "class"
	# - "vendor"
	# - "device"
	# - "subsystem_vendor"
	# - "subsystem_device"

[marquiz]

I was thinking about something like the changes you suggested, but, decided otherwise. I wanted to have all the available options visible in the configmap, this now happens when make yamls. And, I wanted to maintain the example configmap only in one place i.e. nfd-worker.example.conf. Lastly, with your additions the result of make yamls becomes quite ugly as both that example and the content of nfd-worker.conf.example gets into the configmap.

But, on a second thought it would be really nice to have the example also in the templates. I'll sketch up something. BBL
/hold

[marquiz]

Changed the patch so that the configmaps in templates have same data than nfd-worker.conf.example. There's a new templates target for updating them whenever the example config is updated

[marquiz]

/unhold

[ArangoGutierrez]

Your example is waaaay better than mine
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ArangoGutierrez, marquiz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [marquiz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment