-
Notifications
You must be signed in to change notification settings - Fork 54
Issues: operator-framework/operator-controller
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Improvements to internal image unpacking abstractions
kind/design
Categorizes issue or PR as related to design.
v1.x
Issues related to OLMv1 features that come after 1.0
#1345
opened Oct 4, 2024 by
joelanford
[Epic] Combine catalogd and operator-controller into a monorepo
v1.x
Issues related to OLMv1 features that come after 1.0
#1335
opened Oct 3, 2024 by
OchiengEd
9 tasks
[Epic] Add an ability to disable or re-enable a catalog
v1.x
Issues related to OLMv1 features that come after 1.0
#1327
opened Oct 2, 2024 by
LalatenduMohanty
3 of 4 tasks
[epic] Ensure no two ClusterExtensions manage the same underlying object when concurrent reconciles > 1
epic
v1.x
Issues related to OLMv1 features that come after 1.0
#1101
opened Aug 7, 2024 by
everettraven
bug: Misleading error message when no successors available
kind/bug
Categorizes issue or PR as related to a bug.
v1.x
Issues related to OLMv1 features that come after 1.0
#1022
opened Jul 9, 2024 by
joelanford
[epic] operator-controller rejects helm charts that use helm hooks
epic
v1.x
Issues related to OLMv1 features that come after 1.0
#995
opened Jul 1, 2024 by
joelanford
[epic] Support upgrades of OLMv1 itself
epic
v1.x
Issues related to OLMv1 features that come after 1.0
#982
opened Jun 26, 2024 by
joelanford
[epic] Add support for handling helm charts
epic
v1.x
Issues related to OLMv1 features that come after 1.0
#962
opened Jun 21, 2024 by
joelanford
[epic] Support orphan deletion policy
epic
triage/needs-information
Indicates an issue needs more information in order to work on it.
v1.x
Issues related to OLMv1 features that come after 1.0
#775
opened Apr 22, 2024 by
joelanford
[epic] Support interaction similar to OLMv0's OperatorConditions upgrade blocking
epic
triage/needs-information
Indicates an issue needs more information in order to work on it.
v1.x
Issues related to OLMv1 features that come after 1.0
#739
opened Apr 4, 2024 by
joelanford
[epic] Extension health
epic
triage/needs-information
Indicates an issue needs more information in order to work on it.
v1.x
Issues related to OLMv1 features that come after 1.0
#390
opened Aug 31, 2023 by
ncdc
[epic] Migration from v0
epic
triage/needs-information
Indicates an issue needs more information in order to work on it.
v1.x
Issues related to OLMv1 features that come after 1.0
#386
opened Aug 31, 2023 by
ncdc
[epic] User can list ClusterExtension-provided APIs available to them
epic
triage/needs-information
Indicates an issue needs more information in order to work on it.
v1.x
Issues related to OLMv1 features that come after 1.0
#385
opened Aug 31, 2023 by
ncdc
[epic] Ability to configure user/group permissions to an Operator's provided APIs
epic
v1.x
Issues related to OLMv1 features that come after 1.0
#383
opened Aug 31, 2023 by
ncdc
1 task done
[epic] Pre-flight checks for API-based dependencies
epic
triage/needs-information
Indicates an issue needs more information in order to work on it.
v1.x
Issues related to OLMv1 features that come after 1.0
#382
opened Aug 31, 2023 by
ncdc
[epic] Pre-flight checks for cluster constraints
epic
triage/needs-information
Indicates an issue needs more information in order to work on it.
v1.x
Issues related to OLMv1 features that come after 1.0
#376
opened Aug 31, 2023 by
joelanford
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.