-
Notifications
You must be signed in to change notification settings - Fork 39
Issues: konveyor/operator
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
olm issue while deploying konveyor operator
needs-kind
Indicates an issue or PR lacks a `kind/foo` label and requires one.
needs-priority
Indicates an issue or PR lacks a `priority/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
#384
opened Oct 14, 2024 by
Samshiva1524
CR Samples may be useful for demonstrating CR configurations
kind/informational
Information Only. No action required.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/minor
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
triage/unresolved
Indicates an issue that can not or will not be resolved.
#335
opened Jun 13, 2024 by
jmontleon
OWNERS.md Missing
kind/documentation
Categorizes issue or PR as related to documentation.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#283
opened Nov 18, 2023 by
kaovilai
Manifests on release branches (tackle-k8s) reference :latest.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#268
opened Oct 17, 2023 by
jortel
lookup(k8s, cluster_info) has been deprecated in favor of the k8s_cluster_info module
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#232
opened May 17, 2023 by
fabianvf
Further name changes of 'Tackle' to 'Konveyor'
kind/documentation
Categorizes issue or PR as related to documentation.
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#198
opened Apr 14, 2023 by
jwmatthews
Document how to install and access UI from EKS
kind/documentation
Categorizes issue or PR as related to documentation.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
triage/needs-information
Indicates an issue needs more information in order to work on it.
#170
opened Mar 27, 2023 by
jwmatthews
Consider providing a helm chart for installation
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
#137
opened Nov 7, 2022 by
dymurray
ProTip!
Add no:assignee to see everything that’s not assigned.