-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://devopstales.github.io/kubernetes/k3s-etcd-kube-vip/ #7
Comments
Hello, Unfortunately I fail with the following step: There was no error before. I think after creating the manifest (I think the content of this manifest is correct and complete.) Can you please advise how to fix the issue? THX |
Hi @cmonty14. There is no missing step. K3S has a function called autodeploy. Any file found in /var/lib/rancher/k3s/server/manifests will automatically be deployed to Kubernetes in a manner similar to kubectl apply. So check the logs of the k3s. If the kube-vip.yaml can be deployed by k3s check the logs of the kube-vip pod in the kube-system namespace. |
Hi @devopstales, thanks for your reply. When I was investigating this issue I found another deployment guide on YT. Here there are some modifications to the manifest file. Do you confirm that latest kube-vip can load balance services, too? |
@cmonty14 Yes it can be a loadbalancer too. If you carefully read my post it is under the |
Hi @devopstales, the latest version of kube-vip found on docker hub (as of this writing) is v0.4.2. Currently having some issues with the above setup. Observing Thanks. |
@dleeha not 2.3.8 it is 0.3.8. I didn't see this error before but I thin you shod ask for help at https://github.com/kube-vip/kube-vip instead of here. I am not the maintainer of this software. |
Install K3S with k3sup and kube-vip - devopstales
https://devopstales.github.io/kubernetes/k3s-etcd-kube-vip/
The text was updated successfully, but these errors were encountered: