Stay organized with collections
Save and categorize content based on your preferences.
Debug issues using GKE Identity Service pod logs
GKE Identity Service pod logs can help cluster administrators and
developers debug problems and monitor cluster activity.
Based on the severity of the problem, GKE Identity Service logs are
classified using the following severity levels:
INFO[I]: An operational event with high-level details of the actions taken by GKE Identity Service during the processing of requests (such as startup and housekeeping messages). The logs also contain information about expected events that could result in problems. Examples include authentication and workflow checks.
WARNING[W]: An unexpected event that may indicate an underlying problem.
Examples include provider-specific authentication issues.
ERROR[E]: An unexpected problematic event that requires a cluster administrator to fix the issue.
Examples include missing configuration, token exchange failure, and authentication issues.
The following is an example of a typical pod log message:
I0926 09:00:00.000000 12345 foo.cc:10] Skipping Kubernetes Webhook adapter startup since it is not configured.
where,
The prefix I represents the INFO severity level, appended with the log date 0926.
The time follows, with microseconds, in the machine's local timezone.
12345 is a thread ID number.
foo.cc:10 is the source code location where the log description appears (the bracket [ and space are fixed delimiters before the message).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Debug issues using GKE Identity Service pod logs\n================================================\n\nGKE Identity Service pod logs can help cluster administrators and\ndevelopers debug problems and monitor cluster activity.\n\nBased on the severity of the problem, GKE Identity Service logs are\nclassified using the following severity levels:\n\n- **INFO\\[I\\]**: An operational event with high-level details of the actions taken by GKE Identity Service during the processing of requests (such as startup and housekeeping messages). The logs also contain information about expected events that could result in problems. Examples include authentication and workflow checks.\n- **WARNING\\[W\\]**: An unexpected event that may indicate an underlying problem. Examples include provider-specific authentication issues.\n- **ERROR\\[E\\]**: An unexpected problematic event that requires a cluster administrator to fix the issue. Examples include missing configuration, token exchange failure, and authentication issues.\n\nThe following is an example of a typical pod log message:\n\n`I0926 09:00:00.000000 12345 foo.cc:10] Skipping Kubernetes Webhook adapter startup since it is not configured.`\n\nwhere,\n\n- The prefix `I` represents the INFO severity level, appended with the log date `0926`.\n- The time follows, with microseconds, in the machine's local timezone.\n- `12345` is a thread ID number.\n- `foo.cc:10` is the source code location where the log description appears (the bracket `[` and space are fixed delimiters before the message).\n\n| **Note:** You can suppress the prefix globally using the `--nolog_prefix` flag or for a single message the `.NoPrefix()` mutator method.\n\nTo learn more about logging and cluster administration, see [Cluster administration](https://kubernetes.io/docs/concepts/cluster-administration/logging/)."]]
