-
Notifications
You must be signed in to change notification settings - Fork 54
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
Policy-controller failed to validate pods #669
Comments
@prudnitskiy Thanks for opening the issue. I am looking at your logs, but I cannot find any specific error related to the KMS or policy validation. Could you share the error you get when trying to create a pod that matches your policy (mode: enforce)? I think I'll need the rest of the logs to get enough information so I can understand what is the problem. |
This log is for policy reject. Policy successfully rejected the request:
The log message for warning mode looks pretty strange for me anyway |
@prudnitskiy This log output makes sense to me:
I don't see any GKE KMS error fetching the key or anything else. I recommend you to try You could also use the |
Out of curiosity @prudnitskiy, how did you configure your Workload Identity with Policy-controller KSAs? FYI: I recently got this working with this setup:
Curious to know what you are doing on your end, and if this above could help you. |
Description
Any resource deployment in the GKE cluster with google KMS enabled failed to be validated. Validation ends with a stack trace (see below)
Short notes on setup: we use GKE with the workload identity enabled. We use google KMS to validate images.
policy-webhook
service account has permission for GKMS to read and use keys to verify image signatures.Default behavor set to
warn
. Policy has been loaded successfully, no issues. Any validation request ends with the log below:Version
policy-controller: 0.7.0
chart version: 0.5.2 -> 0.5.4
kubernetes version: 1.24.9-gke.3200
The text was updated successfully, but these errors were encountered: