Unable to add new node pool to a route based cluster

Problem

When a user tries to add a new node pool to a route-based cluster through Google Kubernetes Engine, the new node pool addition fails with the following error:

Cannot set max pods constraint on node pool for route-based clusters.

OR

Node pool network_config on a node pool for a route-based cluster should only have enable_private_nodes set.

Environment

  • Google Kubernetes Engine UI

Solution

  1. When adding a new node pool on Cloud Console, instead of clicking on the CREATE button, click Equivalent command line at the bottom of the page next to the CREATE button.
  2. Click RUN IN CLOUD SHELL and execute the command.
  3. This command should run in the cloud shell and fail with a similar error.
  4. To counter the error, remove the --max-pods-per-node "110" option from the end of the command line and execute the command again.
  5. The new node pool creation should be kicked off after the last step.

Cause

This is a known issue with Google Kubernetes Engine interface, which was recently discovered. Please follow the mentioned issue tracker for updates on when it will be resolved.