-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Issues: operator-framework/operator-sdk
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
generate bundle
: Option to use skopeo for resolving image digests
#6868
opened Nov 19, 2024 by
adambkaplan
I... Have a corpse. redis-operator keeps returning.
language/go
Issue is related to a Go operator project
#6854
opened Nov 5, 2024 by
IngwiePhoenix
Installation: WARNING: This key is not certified with a trusted signature!
#6853
opened Nov 2, 2024 by
stefanmeisner
Dynamic namespace handling for ServiceMonitor serverName in operator metrics scraping
#6846
opened Oct 18, 2024 by
iblancasa
Documentation uses deprecated variables for defining namespace scope in manager options
#6843
opened Oct 15, 2024 by
mmeknowis
Handle support for secondary resource provided by CRD when not present at Operator start
language/go
Issue is related to a Go operator project
#6841
opened Oct 12, 2024 by
rwhundley
IPv6 Address Wrapping Issue in CatalogSource Resource
language/go
Issue is related to a Go operator project
#6835
opened Sep 18, 2024 by
dhirajlakhane30
How to troubleshoot a failure during run bundle-upgrade
language/helm
Issue is related to a Helm operator project
#6831
opened Sep 6, 2024 by
etsauer
Go tutorials are referencing old project layout
kind/documentation
Categorizes issue or PR as related to documentation.
#6821
opened Aug 28, 2024 by
maxcao13
helm-operator when creating certificate via secret , diff certificate seen in different pods even after using same certificate from secret
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#6806
opened Aug 8, 2024 by
malli31
How to reconcile built-in types
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#6799
opened Aug 1, 2024 by
NickyHeuperman
Documentation uses deprecated examples of defining namespace scope in manager options
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#6796
opened Aug 1, 2024 by
NymanRobin
Allow IfNotPresent policy when Indicates that an issue or PR should not be auto-closed due to staleness.
operator-sdk run bundle
lifecycle/frozen
#6795
opened Jul 31, 2024 by
kaovilai
Go examples - cleanup does not remove namespace
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#6791
opened Jul 26, 2024 by
m-szalik
generate bundle
: Support overwriting of annotations.yaml
help wanted
#6787
opened Jul 22, 2024 by
adambkaplan
Enable OpenSSF Scorecard to enhance security practices across the project
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#6783
opened Jul 12, 2024 by
harshitasao
Unable to deploy CNF when there are some metrics apiservices are in False or FailedDiscoveryCheck
#6782
opened Jul 12, 2024 by
ansvu
+operator-sdk:csv:customresourcedefinitions:order
does not change order in bundle
language/go
#6771
opened Jun 11, 2024 by
mateusoliveira43
Investigate UBI-micro for Ansible, Helm and SDK base images
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Go CSV Markers to populate specDescriptors for "owned" CRDs from another module
language/go
Issue is related to a Go operator project
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
triage/needs-information
Indicates an issue needs more information in order to work on it.
Generate bundle ignore RelatedImages from config/manifests/bases
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/bug
Categorizes issue or PR as related to a bug.
language/go
Issue is related to a Go operator project
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.