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] config.yaml is not populated with hostvars #138

Closed
marcinkubica opened this issue Feb 15, 2023 · 1 comment
Closed

[BUG] config.yaml is not populated with hostvars #138

marcinkubica opened this issue Feb 15, 2023 · 1 comment

Comments

@marcinkubica
Copy link
Contributor

For example host.ini

[rke2_servers]
master-01 node_labels='["extraLabel0=true"]' node_ip="10.0.0.10" node_name="customName0" bind_address="10.0.0.10" advertise_adress="10.0.0.10" node_external_ip="52.52.52.52" node_taints='["CriticalAddonsOnly=true:NoSchedule"]' cloud_provider_name="aws"

The resulting config will be:

cat /etc/rancher/rke2/conf.yaml 
cloud-provider-name: aws
node-label:
- extraLabel0=true
node-taint:
- CriticalAddonsOnly=true:NoSchedule

Additionally when running with variable rke2_config['node-labels'] or rke2_config['nodte-taint'] resulting config.yaml file is even smaller and will contain just node-label/node-taint respectively (plus server and token for nodes)

ansible-playbook site.yml -v -l master-01 -e '{ "rke2_config" : { "node-label": ["ansibleLabel=true"] }}'
...
cat /etc/rancher/rke2/config.yaml
node-label:
- ansibleLabel=true
@mddamato
Copy link
Contributor

Should be fixed in #144

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants