Customizing nfd-worker's config

[patrykxmatuszak]

Hi,

Is there's any way to customize the nfd-worker's config without building own images?
I wanted to change the labels from vendor to vendor+device id (and possible other), but it seems that after editing configmap -n openshift-nfd nfd-worker operator immediately overwrites with the definition embedded in its container image.

Thanks

[zvonkok]

@ArangoGutierrez PTAL

[patrykxmatuszak]

What is status of the issue? It's rather important for us.

[ArangoGutierrez]

Hi @patrykxmatuszak I am currently working on this on the upstream NFD kubernetes-sigs/node-feature-discovery-operator#36 hope soon will be merged and ported into the OpenShift distribution

[ArangoGutierrez]

@patrykxmatuszak -> kubernetes-sigs/node-feature-discovery-operator#39

once merged upstream, I will try to backport it as soon as I can

[ArangoGutierrez]

Current master now expands the NodeFeatureDiscovery CRD to enable users to modify the CR and define the nfd-worker-conf , or if the operator has already been deployed, users will be able to modify the CR

[ArangoGutierrez]

@patrykxmatuszak please let us know if current master satisfy your use case so we can close this issue :)
thanks for your interest in the project

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[ArangoGutierrez]

@patrykxmatuszak now you can edit and customize nfd-worker config via CR NodeFeatureDiscovery
Is that ok for you, if so can we close this issue
thanks

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.