"static Pod manifest" in DaemonSet docs

[lindhe]

This sounds like a copy-paste error from another part of the docs:

The functionality of kube-vip depends on the flags used to create the static Pod manifest.

website/content/docs/installation/daemonset.md

Line 16 in 12398ba

The functionality of `kube-vip` depends on the flags used to create the static Pod manifest. By passing in `--controlplane` we instruct `kube-vip` to provide and advertise a virtual IP to be used by the control plane. By passing in `--services` we tell `kube-vip` to provide load balancing for Kubernetes Service resources created inside the cluster. With both enabled, `kube-vip` will manage a virtual IP address that is passed through its configuration for a highly available Kubernetes cluster. It will also watch Services of type `LoadBalancer` and once their `service.metadata.annotations["kube-vip.io/loadbalancerIPs"]` or `spec.LoadBalancerIP` is updated (typically by a cloud controller, including (optionally) the one provided by kube-vip in [on-prem](/docs/usage/cloud-provider/) scenarios) it will advertise this address using BGP/ARP. In this example, we will use both when generating the manifest.

website/content/docs/installation/daemonset.md

Line 28 in 12398ba

In order to create an easier experience of consuming the various functionality within kube-vip, we can use the kube-vip container itself to generate our static Pod manifest. We do this by running the kube-vip image as a container and passing in the various [flags](/flags/) for the capabilities we want to enable.

website/content/docs/installation/daemonset.md

Line 52 in 12398ba

With the input values now set, we can pull and run the kube-vip image supplying it the desired flags and values. Once the static Pod manifest is generated for your desired method (ARP or BGP), if running multiple control plane nodes, ensure it is placed in each control plane's static manifest directory (by default, `/etc/kubernetes/manifests`).