openshift / openshift/windows-machine-config-operator
[Bug]: STILL Missing Updated Community Releases
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 52
- Forks
- 77
- Avg merge
- 19h 22m
- Merged PRs (30d)
- 93
Description
Attention
- I am using the community version of WMCO
Version
OKD
Cluster Version
4.19
Platform
Platform agnostic (type=none)
Proxy
No
WMCO Version
6.0.0
Windows version
2022
What happened?
Similar to #2642 I'm running OKD (the community version), and the only community operator available in the Operator Hub is only compatible with K8s 1.24.x (OKD is up to 1.35.x). Please update the community builds - it's been 6 months since #2642 was originally opened, and 3 months since you closed it as "stale", and we still don't have updated community builds.
What did you expect to happen?
I expect the Community versions of the operators to be up-to-date and available in the community Operator Hub.
Steps to reproduce the issue
- Install OKD cluster version 4.19.0
- Attempt to install the Windows Machine Config Operator
Do you have a workaround for this issue?
No.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the community Operator Hub build and release process, then compare the current behavior with issue #2642. Done means updated community operators are available and compatible with OKD 4.19 and its Kubernetes version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100