Explain that static Pods never get evicted under node pressure

content/en/docs/concepts/scheduling-eviction/node-pressure-eviction.md

@@ -354,8 +354,49 @@ will choose to evict pods of lowest Priority first.
 
 If you are running a [static pod](/docs/concepts/workloads/pods/#static-pods)
 and want to avoid having it evicted under resource pressure, set the
-`priority` field for that Pod directly. Static pods do not support the
-`priorityClassName` field.
+`priorityClassName` field for that Pod directly. 
+
+{{< note >}}
+>The kubelet considers all static pods as critical regardless of their `.spec.priorityClassName`.
+>Static pods also pass kubelet admission even if a node does not have enough resources; the kubelet may
+>instead evict another Pod (potentially even evicting a different Pod at a higher priority, if there is no better match).
+
+>You must ensure that you account for resource use when defining static pods on existing nodes.
+{{</ note >}}
+For example, you might follow the following steps to set the `priorityClassName` for a static pod as `xyz-priority`.
+
+```shell
+kubectl get priorityclass
+```
+
+The output is similar to this:
+
+```console
+NAME                      VALUE        GLOBAL-DEFAULT   AGE
+system-cluster-critical   2000000000   false            2m2s
+system-node-critical      2000001000   false            2m2s
+xyz-priority              1000000      false            47s
+```
+
+This is a definition for a static Pod. You would define this directly for the kubelet on a particular node (and not via kubectl)
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: static-web
+  labels:
+    role: myrole
+spec:
+  containers:
+    - name: web
+      image: nginx
+      ports:
+        - name: web
+          containerPort: 80
+          protocol: TCP
+  priorityClassName: xyz-priority
+```
 
 When the kubelet evicts pods in response to inode or process ID starvation, it uses
 the Pods' relative priority to determine the eviction order, because inodes and PIDs have no