pkg log/syslog (netbsd-arm64), const LOG_CRIT = 2
pkg log/syslog (netbsd-arm64), const LOG_CRIT Priority
pkg log/syslog (netbsd-arm64), const LOG_CRON = 72
pkg log/syslog (netbsd-arm64), const LOG_CRON Priority
pkg log/syslog (netbsd-arm64), const LOG_DAEMON = 24
pkg log/syslog (netbsd-arm64), const LOG_DAEMON Priority
pkg log/syslog (netbsd-arm64), const LOG_DEBUG = 7
pkg log/syslog (netbsd-arm64), const LOG_DEBUG Priority

pkg log/syslog (darwin-arm64), const LOG_UUCP = 64
pkg log/syslog (darwin-arm64), const LOG_UUCP Priority
pkg log/syslog (darwin-arm64), const LOG_WARNING = 4
pkg log/syslog (darwin-arm64), const LOG_WARNING Priority
pkg log/syslog (darwin-arm64), func Dial(string, string, Priority, string) (*Writer, error)
pkg log/syslog (darwin-arm64), func New(Priority, string) (*Writer, error)

- 'Priority and Fairness has introduced a new feature called _borrowing_ that allows an API priority level
  to borrow a number of seats from other priority level(s). As a cluster operator, you can enable borrowing
  for a certain priority level configuration object via the two newly introduced fields `lendablePercent`, and

*   Apply algorithm in scheduler by feature gates. ([#52723](https://github.com/kubernetes/kubernetes/pull/52723),[ @k82cn](https://github.com/k82cn))

    * Default value for expendable pod priority cutoff in GCP deployment of Cluster Autoscaler changed from 0 to -10.
    * action required: users deploying workloads with priority lower than 0 may want to use priority lower than -10 to avoid triggering scale-up.

### Other notable changes

- Some apiserver metrics were changed, as follows.
  - `priority_level_seat_count_samples` is replaced with `priority_level_seat_utilization`, which samples every nanosecond rather than every millisecond; the old metric conveyed utilization despite its name.
  - `priority_level_seat_count_watermarks` is removed.

  
  action required

    * Default value for expendable pod priority cutoff in GCP deployment of Cluster Autoscaler changed from 0 to -10.
    * action required: users deploying workloads with priority lower than 0 may want to use priority lower than -10 to avoid triggering scale-up.

- This PR adds the following metrics for API Priority and Fairness.
  - **apiserver_flowcontrol_priority_level_seat_count_samples**: histograms of seats occupied by executing requests (both regular and final-delay phases included), broken down by priority_level; the observations are taken once per millisecond.

### API Priority and Fairness graduates to Beta

Initially introduced in 1.18, Kubernetes 1.20 now enables API Priority and Fairness (APF) by default. This allows `kube-apiserver` to [categorize incoming requests by priority levels](https://docs.k8s.io/concepts/cluster-administration/flow-control/).

### IPv4/IPv6 run