ansible-role-rke2
ansible-role-rke2 copied to clipboard
feature: Rollout restart after /etc/rancher/rke2/config.yaml changed
Summary
Changed made in /etc/rancher/rke2/config.yaml need restart. ie added tls-san, changed network plugin or cluster-cidr.
Issue Type
Feature Idea
same thing for changes regarding a custom registry, so /etc/rancher/rke2/registries.yaml those only become active after rke2-{agent,server} was restarted
Should be solved by https://github.com/lablabs/ansible-role-rke2/pull/113