8000 [Bug] admission controller fails to come online, when reporting is disabled · Issue #13107 · kyverno/kyverno · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Bug] admission controller fails to come online, when reporting is disabled #13107

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
Open
2 tasks done
satheesh23 opened this issue May 9, 2025 · 1 comment
Open
2 tasks done

[Bug] admission controller fails to come online, when reporting is disabled #13107

satheesh23 opened this issue May 9, 2025 · 1 comment
Labels
bug Something isn't working triage Default label assigned to all new issues indicating label curation is needed to fully organize.

Comments

@satheesh23
Copy link

Kyverno Version

1.14.1

Description

kyverno : 1.14.1
policy reporter: v3.1.3
report server: v0.1.3

when we install reporting components (policy controller + policy reporter + policy reporter UI + report server) along with admission controllers, it works as expected.

If we remove or disable the reporting components, after the admission controller pod restarts, fails to come online and goes into crashloopbackoff state.

troubeshooting steps tried,

oc delete validatingwebhookconfiguration kyverno-resource-validating-webhook-cfg
oc delete  mutatingwebhookconfiguration kyverno-resource-mutating-webhook-cfg

oc delete apiservice v1.reports.kyverno.io (managed by reporter)
oc delete apiservice v1alpha2.wgpolicyk8s.io(managed by reporter)

After deleting above resources, admission controller pods complains about the below errors,

2025-05-09T14:32:39Z ERR home/default/github.com/kyverno/kyverno/cmd/kyverno/main.go:689 > failed to start admission reports watcher error="the server could not find the requested resource" logger=setup

Slack discussion

No response

Troubleshooting

  • I have read and followed the documentation AND the troubleshooting guide.
  • I have searched other issues in this repository and mine is not recorded.
@satheesh23 satheesh23 added bug Something isn't working triage Default label assigned to all new issues indicating label curation is needed to fully organize. labels May 9, 2025
@welcome Welcome
Copy link
welcome bot commented May 9, 2025

Thanks for opening your first issue here! Be sure to follow the issue template!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working triage Default label assigned to all new issues indicating label curation is needed to fully organize.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@satheesh23
0