You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nodes in a cluster are not labeled with common labels automatically and users have to run a separate cloud controller to get node labels. This blocks some common application installations that required topology spread or instance type information until the labels are added.
Solution
We should have an option (enabled by default) to have Omni apply well known node labels (via node patch if required) to nodes as part of cluster creation.
Omni already knows information about instance type, zone, and region. But the Kubernetes node labels don't have that information.
It may also be beneficial to continually sync Omni labels with k8s node labels to make troubleshooting and finding instances easier. This could potentially help emulated machines too if the provider was automatically set in omni and in k8s.
Alternative Solutions
Users have to set labels manually via a patch based on Omni node labels.
Notes
Setting the label via a patch also creates the annotation for owned-labels which may not be desired
The text was updated successfully, but these errors were encountered:
Problem Description
Nodes in a cluster are not labeled with common labels automatically and users have to run a separate cloud controller to get node labels. This blocks some common application installations that required topology spread or instance type information until the labels are added.
Solution
We should have an option (enabled by default) to have Omni apply well known node labels (via node patch if required) to nodes as part of cluster creation.
Omni already knows information about instance type, zone, and region. But the Kubernetes node labels don't have that information.
It may also be beneficial to continually sync Omni labels with k8s node labels to make troubleshooting and finding instances easier. This could potentially help emulated machines too if the provider was automatically set in omni and in k8s.
Alternative Solutions
Users have to set labels manually via a patch based on Omni node labels.
Notes
Setting the label via a patch also creates the annotation for owned-labels which may not be desired
The text was updated successfully, but these errors were encountered: