-
Notifications
You must be signed in to change notification settings - Fork 909
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
resource_labels added to the node_config nodepool #2317
resource_labels added to the node_config nodepool #2317
Conversation
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @fulyagonultas, it seems labels and resource_labels serve different purposes. Can you keep labels and add a new field/variable for resource_labels? And you'll probably want to do the same in the gke-clustar-standard
and gke-cluster-autopilot
hi @juliocc, thanks for the heads-up! |
hi @fulyagonultas, we just had an internal discussion about this and we think the best approach is the following:
So in summary, keep var.labels as it is and add a new variable/field for kubernetes labels. Can you make these changes? Sorry for the mixup, but I didn't fully understand what you were trying to do initially. |
@fulyagonultas I took the liberty to apply the changes. I'm working through the tests now |
…rce-labels-nodepool
Resource labels is needed in node_config block of nodepool module
Checklist
I applicable, I acknowledge that I have:
terraform fmt
on all modified filestools/tfdoc.py