Change:
// pods. func (kl *Kubelet) GetPods() []*v1.Pod { pods := kl.podManager.GetPods() <del> // a kubelet running without apiserver requires an additional // update of the static pod status. See #57106 </del> for i, p := range pods { <ins> // Pod cache does not get updated status for static pods. // TODO(tallclair): Most callers of GetPods() do not need pod status. We should either parameterize this, // or move the status injection to only the callers that do need it (maybe just the /pods http handler?). </ins> if kubelettypes.IsStaticPod(p) { if status, ok := kl.statusManager.GetPodStatus(p.UID); ok { <del> klog.V(2).InfoS("Pod status updated", "pod", klog.KObj(p), "status", status.Phase) </del> // do not mutate the cache p = p.DeepCopy() p.Status = status

Discussion:
<!-- Please only use this template for submitting enhancement requests --What would you like to be : I would like to ask to increase the log level for this line: Why is this needed: I do not see the necessity to show every time the static pod has the status updated. It can flood the logs with the message. I do not know if there is a reason for that. I believe it is a matter of taste. Furthermore, the adding this piece of code, the log was not there. The log line has being in a
/sig node
I'll be happy to send a merge request for this issue. But I just need to know if this make sense to the community or not.
According to my quick research, this log is in during fixing a regression issue. Agree with you. I think it makes sense to use a lower log level as the bug is already fixed. However, I'm not the owner of kubelet. Let node/kubelet owner make the decision.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
/remove-lifecycle stale
is the issue that it logs the same status over and over? Or that status being changed very often?
/triage accepted I agree V(2) seems a bit high for this. Feel free to submit a PR to drop to 3.
what is the reason for rapid status change?
It the almost the same message. This is an example: I'm willing to send the PR.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at .

/lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Reopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /close [1]:
Closing this issue. <detailsIn response to : The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closedReopen this issue or PR with Mark this issue or PR as fresh with Offer to help out with [Issue Triage][1] Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/reopen /assign This is still an issue.
Reopened this issue. <detailsIn response to : /reopen /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-lifecycle rotten As PR is still open