Skip to content
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

bug: Can not provision cluster #253

Open
hoangphuocbk opened this issue Oct 4, 2024 · 1 comment
Open

bug: Can not provision cluster #253

hoangphuocbk opened this issue Oct 4, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@hoangphuocbk
Copy link
Contributor

Summary

after this commit https://github.com/lablabs/ansible-role-rke2/pull/246/files

{% if rke2_bind_address is defined %}
bind-address: {{ rke2_bind_address }}
{% endif %}

the rke2 cluster can not provision when we use kube-vip, because bind-address should be listened on 0.0.0.0 rather specific one on server nodes.

Issue Type

Bug Report

Ansible Version

abc

Steps to Reproduce

Expected Results

abc

Actual Results

abc
@hoangphuocbk hoangphuocbk added the bug Something isn't working label Oct 4, 2024
@MonolithProjects
Copy link
Collaborator

Hi @hoangphuocbk, this is optional. You don't have to use this variable. If it's not set, the RKE2 default value for bind-address is 0.0.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants