-
Notifications
You must be signed in to change notification settings - Fork 762
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
"Object 'Kind' is missing in 'null'" #3743
Comments
Thanks for the report @alex-berger! There are few reasons why req.Object.Raw could be nil:
To help further debug the issue, please check the k8s API server logs to inspect the request object that ended in error e.g. |
@ritazh In our case Gatekeeper v3.18.0 was installed via Helm Chart, actually it was upgrade from version v3.15.1 (via FluxCD / GitOps).
Interestingly, we have not found anything in the k8s API server logs that would indicated failing webhook calls. But, that might well be, because the webhook's Handler function is not failing but just logging the error and then continues (i.e. does not immediately return). isExcludedNamespace, err := h.skipExcludedNamespace(&req.AdmissionRequest, process.Webhook)
if err != nil {
h.log.Error(err, "error while excluding namespace")
} |
@alex-berger can you provide the steps to reproduce? I am not able to reproduce the same on my end. Did you update to 3.18.1? if so, after 3.18.1 are you still facing the same issue? |
What steps did you take and what happened:
After upgrading to Gatekeeper 3.18.0 we are observing below error message (exactly 4 messages every 2 minutes) and now I am wondering what might cause this.
Here a formatted version of the error message's stack trace:
It looks like this is because skipExcludedNamespace is calling
deserializer.Decode(nil, ...)
asreq.Object.Raw
seems to be nil.What did you expect to happen:
No errors :-)
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
3.18.0
v1.30.6-eks-7f9249a
The text was updated successfully, but these errors were encountered: