revive kmsg channel if closed

[daveoy]

would like to start a conversation around revival of closed kmsg channels.

#1004 supplies a recovery mechanism which, when configured in the plugin's config, will revive a closed kmsg channel.

i have observed that the channel to /dev/kmsg can be closed unexpectedly in a couple of scenarios:

• when a daemonset rollout is being performed on a node under high load, and
• during regular operation when a node is experiencing extremely high load

#1004 could potentially use some improvement, if anyone has any better ideas. what im trying to avoid is re-initializing the conditions set by the watcher.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten