-
Notifications
You must be signed in to change notification settings - Fork 551
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
Outdated operators on OperatorHub #1742
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Unstale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Unstale |
If this is a concern, please address in operator-framework/community-operators. The OLM maintainers do not maintain the community catalogs. Thanks! |
Type of question
Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
General context and help, community best bractices
Question
What did you do?
I installed OLM and tried to install the Minio and Postgres operators.
What did you expect to see?
I expected to see the latest available release installed of the above operators.
What did you see instead? Under which circumstances?
I got seriously outdated operators, so I ended up removing them - then finally removing OLM as well as I have no use case besides these operators 😢
Postgres:
Minio:
Environment
Additional context
OLM is a great tool but packages should be maintained. I could open two tickets for these operators for an OLM package update but I suppose this is a more general issue that needs to be solved on the OLM-side. Maybe enforce at least monthly updates to keep the packages from being labeled as outdated in the OperatorHub?
The text was updated successfully, but these errors were encountered: