Skip to content
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

Enabling audit logs fails during patch operation #568

Open
akgalwas opened this issue Dec 16, 2024 · 0 comments
Open

Enabling audit logs fails during patch operation #568

akgalwas opened this issue Dec 16, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@akgalwas
Copy link
Contributor

Description

KIM doesn't correctly handle a scenario with enabling audit logs for a runtime that previously had audit logs disabled.

Steps to reproduce

  1. Create a Runtime CR for a region that doesn't have audit log configuration. Make sure KIM has auditlogmandatory parameter set to false.
  2. Wait until the shoot is reconciled. Confirm the audit log extension is not included in spec.extensions
  3. Provide missing audit log configuration for the Runtime's region.
  4. Modify any property to cause reconciliation.
  5. Notice the Runtime has Failed status. The error message is Gardener API shoot patch error: admission webhook "validator.shoot-auditlog-admission.extensions.gardener.cloud" denied the request: missing or invalid referenced resource: auditlog-credentials

Expected result

KIM should enable audit logs in all cases no matter what is current state of the shoot.

Actual result

Enabling audit logs for a runtime with audit logs disabled fails.

@tobiscr tobiscr added the kind/bug Categorizes issue or PR as related to a bug. label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants