Issues: operator-framework/ansible-operator-plugins
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
Outdated and vulnerable golang x/net version
area/dependency
Issues or PRs related to dependency changes
#76
opened May 15, 2024 by
jperezdealgaba
Outdated and vulnerable golang protobuf dependency
area/dependency
Issues or PRs related to dependency changes
#75
opened May 15, 2024 by
jperezdealgaba
Underlying Go does not interpret folder structure as Ansible based
#63
opened Apr 11, 2024 by
Praveenk8051
Remove ComponentConfig once it is deprecated in controller-runtime
#40
opened Oct 18, 2023 by
oceanc80
ask for ansible-operator for UBI9 , so far still only see UBI8, need operator based on UBI9/RHEL9
#29
opened Aug 11, 2023 by
wying3
Add ansible watch config to run for every update type
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.
#30
opened Aug 1, 2023 by
jutley
Molecule scenarios not generated as documented
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.
#32
opened Jul 4, 2023 by
paterczm
Question: How to omit job events for Ansible operator?
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
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.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#19
opened Jun 1, 2023 by
el-pako
ansible-operator: ignore existing resources at startup or conditional watches in watches.yaml
triage/needs-information
Indicates an issue needs more information in order to work on it.
#20
opened May 3, 2023 by
jmazzitelli
Selector on watches.yaml not honoured
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
triage/support
Indicates an issue that is a support question.
#31
opened Feb 14, 2023 by
anupchandak
e2e-ansible-molecule test improvements
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
#21
opened Apr 26, 2022 by
asmacdo
Objects created without ownerReference injected when using force in k8s ansible module
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#33
opened Sep 29, 2021 by
Roia5
feature: dynamic inventory of resources created by a CR of an ansible operator
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#22
opened May 6, 2021 by
jobcespedes
Ansible using the same default port that is used for Go and Helm
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#23
opened Dec 17, 2020 by
camilamacedo86
For Ansible-based operator, remove the deprecated ping endpoint
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
#24
opened Dec 17, 2020 by
camilamacedo86
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-04-24.