You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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.
Attention
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
The text was updated successfully, but these errors were encountered: