Second scheduler as static pod, not deployment?

Hi all,

I noticed documents how to configure a second scheduler as a deployment; the steps there work for me. However, as by default, schedulers are deployed as static pods (as far as I can tell), wouldn’t it make sense to be consistent and deploy as a static pod as well? Or is the best practice now to stay away from static pods as much as possible?

I posted more detail at, where I go in depth about the steps I went through. The main question I have for this board is - how can I translate the steps in the documentation for a static pod?

Cluster information:

Kubernetes version: 1.18.x
Cloud being used: (put bare-metal if not on a public cloud) bare-metal
Installation method: kubeadm
Host OS: Ubuntu 16.04
CNI and version: weave 2.7.0
CRI and version: Docker

You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.