It's currently very hard to know what the default values are for variables. Some have documentation for what their default values are, but far from all of them.

The K3s docs instruct you to put the yaml files in an auto deploy directory before installation of K3s which makes it seem this directory is only used during setup. The link to the K3s documentation is also wrong, so it's harder to read up on what the directory actually does.

In reality the contents of the directory are applied during every boot of the server which caused me some headaches before I realized what was going on as kube-vip kept gettiing reverted to my initial configuration after I rebooted my initial K3s server.

Please correct the link to this one and maybe update the instructions to make it more clear what that directory does and why it's important to put the files there before installation, if it even is important?

It says here that Control Plane LoadBalancing with ipvs is supported:

It says here that "the HTTP loadbalancing was removed leaving just HA for the control plane":

As part of our ongoing effort to cncf/techdocs#198, we noticed that the website does not pass the trademark criteria on CLOMonitor.

To fix this:
Head to the source code of the website. In the <footer> section, add a disclaimer or link to the Linux foundation trademark disclaimer page:

Disclaimer

<footer>
   <p>The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, 
         please see our <a href="https://www.linuxfoundation.org/legal/trademark-usage">Trademark Usage page</a>.
   </p>
</footer>

Link

 <footer>
      <ul>
          <li><a href="https://www.linuxfoundation.org/legal/trademark-usage">Trademarks</a></li>
      </ul>
 </footer>

Hi, I'd like for the documentation to not show --taint as required for kube-vip as Daemonset.

I've really enjoyed setting up kube-vip on the control plane with VIP and LB using static pods and BGP. Currently running v0.6.3. I set up the cloud-provider and created a configmap in kube-system called kubevip that had data.cidr-global: 10.245.0.0/18. I have a kubernetes/ingress-nginx controller service of type loadbalancer with spec.externalTrafficPolicy: local. I've been reading a few of the open issues on the kube-vip project around this, and they all seem to be treated like this fuctionality is implemented, yet I was getting <pending> for external IPs on loadbalancers with externalTrafficPolicy: local. From the documentation it seems like a kube-vip instance would need to run on a worker. But the pages mostly feel like they address control plane availability. There is some mention of service VIPs and loadbalancing, and the existence of options like --controlplane and --services implied to me that one could run kube-vip on workers without anything related to the control-plane going on. So far so good.

I tried to generate a manifest for a daemonset for kube-vip, to run kube-vip pods on my cluster. My control plane is still using static pods, is there a way to migrate to a controlplane daemonset after kubeadm standup or should I leave them as is? I figured I could have a daemonset limit kube-vip to being run on all worker nodes, just not controlplane. My limited kubernetes knowledge aside, it turns out that happens when there aren't any specific node selectors (not sure what they're called off-hand) for the daemonset, or something along those lines.

To not include affinity rules, --taint can be left out and when applied to the cluster, I have a kube-vip pod on each worker performing service elections and I've successfully had an external IP issued to my ingress-nginx.

The point of this issue is to address the documentation's use of "Required for kube-vip as Daemonset" around --taint. I don't believe it's true --taint is required, as removing that option from the command generating my manifest solved the issue I had been trying to address.

Could that requirement be removed and some clarifications be made around daemonset or static pod (would anyone bother with this approach for workers?) for kube-vip on workers? And around whether both control-plane and workers should use --services and --servicesElection especially considering I've deployed both static pods and a daemonset?

Cheers :)

I think your recent commit changing the URL interferes with accessing the manifests.

https://kube-vip.io/manifests/rbac.yaml
via
https://kube-vip.io/docs/installation/

Control Plane using either leader election

According to the documentation, there is no variable named port. Do you mean lb_port here?

Hi,

When trying to install kube-vip twice (one for control plane and one fore service), I was struggling with :

time="2024-04-23T08:21:33Z" level=fatal msg="listen:listen tcp :2112: bind: address already in use\n"

I don't see any information from the page "Flags and Environment Variables" to configure Prometheus HTTP server with promethes_serveur ?

Could we add this information in this page, not only in https://kube-vip.io/docs/usage/multi_tenancy/?query=multi#prometheus-conflicts ?

Thank you.
Guillaume

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.