NFD operator uses outdated config

[jaedolph]

When attempting to install the openshift-nfd operator using this repo, several containers fail to launch or are crashlooping due to the "latest" tag being hardcoded in the NodeFeatureDiscovery config. This should be removed so that the operator can use the correct versions of containers based on digests rather than this latest tag.

The spec.customConfig field also appears to be deprecated, and causes a sync issue in ArgoCD.

[jaedolph]

The looks like it was added in this commit: bab36fc

The bug that this change was working around appears to be fixed now. We should remove the workaround so it doesn't cause the new version of the operator to crash.

[pittar]

@jaedolph , can you submit a PR for this?

[jaedolph]

Found in the NFD operator where they fixed it: openshift/cluster-nfd-operator@49e1162

[jaedolph]

@jaedolph , can you submit a PR for this?

Yeah I will work on fixing it in a PR. I have also raised a PR for the operator repo here: openshift/cluster-nfd-operator#454

[jaedolph]

PR is here: #379

[jaedolph]

Btw, I also found out where they removed the customConfig field: openshift/cluster-nfd-operator@f09d507

I have created a Jira issue to update the NFD docs too: https://issues.redhat.com/browse/OSDOCS-16234