redhat-cop / redhat-cop/gitops-catalog
NFD operator uses outdated config
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 383
- Forks
- 184
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the NodeFeatureDiscovery configuration in this repository and search for the hardcoded "latest" tag and spec.customConfig. Compare the configuration with the current operator schema and verify the rendered manifests; done means container versions resolve by digest and ArgoCD no longer reports a sync issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100