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

fix: nodepool autoscaling vars avail in GKE 1.24.1 result in conflicts. Change default behavior to null #1554

Conversation

Aurelian-Shuttleworth
Copy link
Contributor

Changes introduced in feat: add nodepool autoscaling vars avail in GKE 1.24.1 result in conflicts when using total limits.

Currently, google_container_node_pool resource states that total and per zone limits can't be used together.

This change removes the default behaviour where min and max are provided by default if autoscaling is enabled.

@google-cla
Copy link

google-cla bot commented Feb 2, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@comment-bot-dev
Copy link

@Aurelian-Shuttleworth
Thanks for the PR! 🚀
✅ Lint checks have passed.

@apeabody
Copy link
Contributor

apeabody commented Feb 2, 2023

Thanks for the contribution @Aurelian-Shuttleworth, here is the int check error message:

Error: error creating NodePool: googleapi: Error 400: Node_pool_autoscaling.max_node_count and node_pool_autoscaling.total_max_node_count cannot be both set to zero., badRequest

  with module.example.module.gke.google_container_node_pool.pools["default-node-pool"],
  on ../../../modules/private-cluster/cluster.tf line 383, in resource "google_container_node_pool" "pools":
 383: resource "google_container_node_pool" "pools" {
}
    apply.go:34: 
        	Error Trace:	/workspace/test/integration/private_zonal_with_networking/apply.go:34
        	            				/workspace/test/integration/private_zonal_with_networking/terraform.go:397
        	            				/workspace/test/integration/private_zonal_with_networking/terraform.go:407
        	            				/workspace/test/integration/private_zonal_with_networking/terraform.go:431
        	            				/workspace/test/integration/private_zonal_with_networking/stages.go:31
        	            				/workspace/test/integration/private_zonal_with_networking/terraform.go:431
        	Error:      	Received unexpected error:
        	            	FatalError{Underlying: error while running command: exit status 1; 
        	            	Error: error creating NodePool: googleapi: Error 400: Node_pool_autoscaling.max_node_count and node_pool_autoscaling.total_max_node_count cannot be both set to zero., badRequest
        	            	
        	            	  with module.example.module.gke.google_container_node_pool.pools["default-node-pool"],
        	            	  on ../../../modules/private-cluster/cluster.tf line 383, in resource "google_container_node_pool" "pools":
        	            	 383: resource "google_container_node_pool" "pools" {
        	            	}
        	Test:       	TestPrivateZonalWithNetworking

@Aurelian-Shuttleworth
Copy link
Contributor Author

Hello, @apeabody ^_^ I meant this PR as a backup for my other PR where the default behaviour is kept. If that approach is not preferred, I will work on fixing the tests so that this version passes code checks and I can remove the draft mark.

@apeabody
Copy link
Contributor

apeabody commented Mar 3, 2023

Hi @Aurelian-Shuttleworth with #1562 merged, is this PR still needed? Thanks!

@github-actions
Copy link

github-actions bot commented May 2, 2023

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label May 2, 2023
@github-actions github-actions bot closed this May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants