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.

Sign up for GitHub

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

Jump to bottom

[RFE] Improve the UX around Catalog images on authenticated registries #1789

Closed
awgreene opened this issue Oct 1, 2020 · 3 comments
Closed

[RFE] Improve the UX around Catalog images on authenticated registries #1789

awgreene opened this issue Oct 1, 2020 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/unresolved Indicates an issue that can not or will not be resolved.
Milestone
Backlog

Comments

@awgreene
Copy link
Member

awgreene commented Oct 1, 2020

Feature Request

Is your feature request related to a problem? Please describe.
As an olm user, I want to fully understand the state of my catalogs by looking at CatalogSource's status.

Describe the solution you'd like

  • Catalog status reports on invalid/duplicate/otherwise malformed Operators
  • Catalog supports specifying a reference to a pull secret for authenticated registries
@awgreene awgreene added this to the Backlog milestone Oct 1, 2020
@awgreene awgreene changed the title Improve the UX around Catalog images on authenticated registries [RFE] Improve the UX around Catalog images on authenticated registries Oct 1, 2020
@stale
Copy link

stale bot commented Nov 30, 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 Nov 30, 2020
@openshift-ci-robot openshift-ci-robot added triage/unresolved Indicates an issue that can not or will not be resolved. and removed wontfix labels Dec 1, 2020
@stale
Copy link

stale bot commented Mar 2, 2021

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contribution.
For more help on your issue, check out the olm-dev channel on the kubernetes slack [1] and the OLM Dev Working Group [2] [1] https://kubernetes.slack.com/archives/C0181L6JYQ2 [2] https://github.com/operator-framework/community#operator-lifecycle-manager-wg

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 2, 2021
@stale
Copy link

stale bot commented Mar 9, 2021

This issue has been automatically closed because it has not had any recent activity. Thank you for your contribution.

@stale stale bot closed this as completed Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@awgreene @openshift-ci-robot