AKS - Scheduling on system node pool

[ibm-bersch]

It is best practice for AKS setups to use the CriticalAddonsOnly=true:NoSchedule taint to prevent application pods from being scheduled on system node pools. See System and user node pools

Therefore I would suggest to update documentation to specify following in values.yaml when deploying the falcon sensor to AKS and CriticalAddonsOnly taint on system node pool:

node:
  # ...
  daemonset:
    # ...
    tolerations:
      # ...
      # Allow schedule on system node pools
      - key: "CriticalAddonsOnly"
        operator: "Exists"
        effect: "NoSchedule"

And/or add it commented out to the values.yaml