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

[feature] Omni to set node-role.kubernetes.io label #751

Open
TimJones opened this issue Dec 2, 2024 · 0 comments
Open

[feature] Omni to set node-role.kubernetes.io label #751

TimJones opened this issue Dec 2, 2024 · 0 comments

Comments

@TimJones
Copy link
Member

TimJones commented Dec 2, 2024

Problem Description

Omni has MachineSet visible in the UI grouping the nodes in a helpful way, but current Talos config and Kubernetes security restrictions don't allow for easily setting the node-role.kubernetes.io/<role> label.

Currently an operator or priviledged access process is required to do the equivilent of kubectl label node <name> node-role.kubernetes.io/<role>: "".

Omni has the higher privilege required and the equivalent node/group mapping that could be useful for simple quality-of-life feature.

Solution

Omni can use the MachineSet name to assign the node role label in Kubernetes.

i.e.

MachineSet name: storage -> Node label: node-role.kubernetes.io/storage: "Managed by Omni"
MachineSet name: loadbalancer -> Node label: node-role.kubernetes.io/loadbalancer: "Managed by Omni"
MachineSet name: worker -> Node label: node-role.kubernetes.io/worker: "Managed by Omni"

Alternative Solutions

Stick with operator-maintained labels :)

Notes

Could be a toggle-able feature.

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

No branches or pull requests

1 participant