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.

Sign up for GitHub

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

Jump to bottom

OneKE: Making rke2-server impossible to run in non-master nodes #194

Open
dgarcia18 opened this issue Feb 3, 2025 · 0 comments
Open

OneKE: Making rke2-server impossible to run in non-master nodes #194

dgarcia18 opened this issue Feb 3, 2025 · 0 comments
Labels
category: oneke OpenNebula Kubernetes appliance

Comments

@dgarcia18
Copy link
Contributor

Starting the rke2-server systemd service in a non-master OneKE node leads to an inconsistent etcd db state after reboot. This could be avoided by "blunting" the rke2-server service in non-master nodes.
@sk4zuzu sk4zuzu added the category: oneke OpenNebula Kubernetes appliance label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category: oneke OpenNebula Kubernetes appliance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sk4zuzu @dgarcia18