openshift / openshift/windows-machine-config-operator

[feature request]: Community version wmco supports for k8s version of 1.24 and 1.25

Open
#3,519 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

lifecycle/frozen
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

vSphere

Proxy

Yes, with HTTPS

WMCO Version

6.0.0

Windows version

2022

What happened?

In the OKD documentation, I noticed that the Windows Machine Config Operator is listed as supported. However, it appears that the operator is not actively maintained in the Community Operator Hub.

The version currently available in the community catalog is 6.0.0, which only supports Kubernetes versions 1.25 and 1.24. Our environment, however, is running OKD 4.19 with Kubernetes 1.32.

Is there any way to leverage and install the operator in this setup? I attempted to build the operator from source using the instructions provided in the Dockerfile, but the registry references within the Dockerfile point to private OpenShift repositories, which are inaccessible externally.

What did you expect to happen?

It would be great if the operator were published publicly in a ready-to-install form, or if the Community Operator Hub version could be actively maintained.

Steps to reproduce the issue

Just install community windows machine config operator, it will throw you an error stating version won't support in the deployment logs in openshift-windows-machine-config-operator namespace

Image
Do you have a workaround for this issue?

no

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Dockerfile and the operator build instructions, then inspect the Community Operator catalog entry and the deployment logs in the openshift-windows-machine-config-operator namespace. Determine what is required to support OKD 4.19/Kubernetes 1.32 and make the operator publicly installable; done means a ready-to-install community version no longer reports an unsupported Kubernetes version.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go, kubernetes
Domain
devops, infrastructure, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.