Skip to content
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

Closed
immanuelfodor opened this issue Aug 27, 2020 · 5 comments
Closed

Outdated operators on OperatorHub #1742

immanuelfodor opened this issue Aug 27, 2020 · 5 comments

Comments

@immanuelfodor
Copy link

immanuelfodor commented Aug 27, 2020

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

  • operator-lifecycle-manager version: v0.15.1
  • Kubernetes version information:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.8", GitCommit:"9f2892aab98fe339f3bd70e3c470144299398ace", GitTreeState:"clean", BuildDate:"2020-08-13T16:12:48Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-15T16:51:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
  • Kubernetes cluster kind: RKE

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?

@stale
Copy link

stale bot commented Oct 26, 2020

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.

@stale stale bot added the wontfix label Oct 26, 2020
@immanuelfodor
Copy link
Author

Unstale

@stale stale bot removed the wontfix label Oct 26, 2020
@stale
Copy link

stale bot commented Dec 25, 2020

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.

@stale stale bot added the wontfix label Dec 25, 2020
@immanuelfodor
Copy link
Author

Unstale

@stale stale bot removed the wontfix label Dec 25, 2020
@ecordell
Copy link
Member

If this is a concern, please address in operator-framework/community-operators. The OLM maintainers do not maintain the community catalogs. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants