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
We've noticed that on our Openshift clusters that were recently updated to version 4.16, we cannot find anymore the MinIO operator in the OperatorHUB list. We can find this however on lower Openshift versions, like 4.15.
We extensively use the MinIO service as part of our Loki logging solution on our Openshift clusters.
Can you let us know if something changed ? And how can we get the operator back ?
Thank you.
Your Environment
Version used (minio-operator): latest
Environment name and version: Openshift 4.16 (kubernetes 1.29.8)
The text was updated successfully, but these errors were encountered:
I had to enable the Marketplace in the OperatorHub:
Administration | Cluster Settings | Global Configuration | OperatorHub
I changed the configuration to enable the Marketplace, waited for the catalog to update, and then it was available again. I am not sure if this will help your particular situation, but I had a similar situation with the operator being unavailable.
That is correct. Moving forward, MinIO will only be available via AIStor in OperatorHub. Starting with OpenShift version 4.17 and beyond, the public operator will no longer be published.
In other words, for those requiring an operator in OpenShift version 4.17 or later, AIStor must be installed, and a license will be required. This is now a commercial solution for OpenShift.
Expected Behavior
We've noticed that on our Openshift clusters that were recently updated to version 4.16, we cannot find anymore the MinIO operator in the OperatorHUB list. We can find this however on lower Openshift versions, like 4.15.
We extensively use the MinIO service as part of our Loki logging solution on our Openshift clusters.
Can you let us know if something changed ? And how can we get the operator back ?
Thank you.
Your Environment
minio-operator
): latestThe text was updated successfully, but these errors were encountered: