How to apply different detection rules based on the SKUs of different nodes

[ymygogogo]

How to apply different detection rules based on the SKUs of different nodes

For example:

https://github.com/Azure/azurehpc-health-checks
https://github.com/mej/nhc

[ymygogogo]

Because there are different specifications of servers in my cluster, but I want to manage it through the helm chart method. I think, perhaps a k8s operator is needed, which can start the npd instances based on the node specifications you define.

[hakman]

@ymygogogo you can run multiple instances of NPD, each one with its on config and node selector:
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#running-pods-on-select-nodes

[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