Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node Feature Discovery Operator failing to properly default image in operator #344

Open
montaguethomas opened this issue Jan 24, 2024 · 3 comments · May be fixed by #345
Open

Node Feature Discovery Operator failing to properly default image in operator #344

montaguethomas opened this issue Jan 24, 2024 · 3 comments · May be fixed by #345

Comments

@montaguethomas
Copy link

Looks like this fork/mirror is updated from the upstream projects from time to time. The sync for 4.11 was done very poorly and then while finishing/fixing the sync merge problems that were committed, the PR [1] to sync with upstream for 0.5.0 removed the required patch [2][3] to allow things to work without overrides to NodeFeatureDiscovery objects.

[1] #266
[2] 055e871
[3] #187

@openshift-bot
Copy link
Contributor

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-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 24, 2024
@montaguethomas
Copy link
Author

Pending respond on PR: #345

@montaguethomas
Copy link
Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants