Proposal: Support configuring rule.Reason as a Sprintf format string

[jessehu]

Hi folks, I'd like to make a proposal to support configuring rule.Reason as a Sprintf format string and formatting it with the matched capturing groups in rule.Pattern. This feature can support the case when a pattern can match multi reasons. For example, there are many kind of Nvidia GPU Xid errors in dmesg log. We can defined a reason string "NvidiaGPUXid%s" and use the matched Xid 31/45/79 to replace "%s" in the reason, so no need to define a dedicated reason for each Xid error.

"NVRM: Xid (PCI:0000:9A:00.0): 31, Ch 00000010"
"NVRM: Xid (PCI:0000:9A:00.0): 45, Ch 00000010"
"NVRM: Xid (PCI:0000:9A:00.0): 79, Ch 00000010"

[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