Skip to content

[Bug]: Missing community releases #2642

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

Open
1 task done
outofrange opened this issue Jan 23, 2025 · 2 comments
Open
1 task done

[Bug]: Missing community releases #2642

outofrange opened this issue Jan 23, 2025 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@outofrange
Copy link

Attention

  • I am using the community version of WMCO

Version

OKD

Cluster Version

4.15

Platform

vSphere

Proxy

No

WMCO Version

6.0.0

Windows version

2022

What happened?

I'm using OKD 4.15, for which the OperatorHub only offers to install wmco 6.0.0 - which is only compatible with 4.11 (I created this PR to mark it as such).

I also created an issue to add newer versions of the Community WMCO to the catalog - but are there even newer versions?
On quay.io, I could only find 4.14.

What did you expect to happen?

I expected to be able to install a compatible community version of WMCO in OKD 4.15

Steps to reproduce the issue

Try to install WMCO through OperatorHub

Do you have a workaround for this issue?

no

@sebsoto
Copy link
Contributor

sebsoto commented Jan 23, 2025

Hi @outofrange
Thanks for opening this issue. We are currently moving to a new build system for the containers we ship and the hope is that this will allow for us to release the community version of the operator easier. I'm not able to give an estimate for the timeline for that at the moment.

@openshift-bot
Copy link

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, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants