Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Issue summary: When GKE cluster has a node pool that should scale to 0, some of the core pods such as ml-pipeline-ui can end up moved to that node pool, preventing the node pool from scaling to 0.
We can set nodeSelector/Affinity after setting up AI Platform Pipelines, but saw this as a potential source of future problems as we need to write the configuration steps themselves.
Suggestions (optional) : We would like if there was a way to restrict the core pods such as ml-pipeline-ui to a certain node pool upon initial setup of AI platform pipelines.
This feature request has been forwarded to AI Platform Team so that they may evaluate it. There is no timeline or implementation guarantee for feature requests. All communication regarding this feature request is to be done here.