-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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: add target tags to node_pool_auto_config
for standard clusters
#2118
fix: add target tags to node_pool_auto_config
for standard clusters
#2118
Conversation
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.
@apeabody I'm not sure this example is one you'd want in examples
-- I think I saw something about that; in that case, do I just fold the whole example into fixtures
? Or should I just add more comments or adjust the sample code slightly?
1c97eef
to
5882a43
Compare
/gcbrun |
Hi @wyardley! I think it's fine to add a relevant example, although we have to be careful with the concurrent test resource usage (might need to also waitFor a subsequent step). While this repo has a build/int.cloudbuild.yaml
|
Yeah, I guess seemed a little niche of a use case; obviously someone copying that one without thinking about what it's doing could end up opening up network holes unnecessarily? And not sure if we should adjust the wording or comments anywhere, or make a more descriptive directory name? I also picked simple regional as the base for this more or less arbitrarily. I'll add in the snippet you suggested for the Cloudbuild config (should maybe remove the lint one at some point?) and we can see how it goes. If the fixture with the expected content is too far off base to adjust, I will probably need your help to figure out how that should be updated / adjusted as well. |
fc75afc
to
200550d
Compare
/gcbrun |
Sure: #2120 |
Looks like this will need to also wait on a longer destroy for resource availability.
|
Are you suggesting to bump the retry interval in |
Sorry - Typo, that should be "later", not "longer. Like this example: https://github.com/terraform-google-modules/terraform-google-kubernetes-engine/blob/master/build/int.cloudbuild.yaml#L458 |
Since there's no explicit init step for this one, add it to the apply, right? Is 336cbff what you had in mind? |
812e4d0
to
336cbff
Compare
Yeah - As there is now an init all, we shouldn't need the per test inits, and ideally can be removed at some point. Looks good, let's see how the tests go: /gcbrun |
FYI: Any step you depend on has to be "earlier" in the cloudbuild file.
|
da4d74d
to
9eac6e7
Compare
/gcbrun |
1 similar comment
/gcbrun |
Are we getting closer to a real failure yet? I can try to do the local setup if needed. |
I don't think so, there is an API change which is breaking the test data as of this morning. Will re-run this once that is updated. |
/gcbrun |
3 similar comments
/gcbrun |
/gcbrun |
/gcbrun |
@apeabody this should almost definitely still be failing at least partially because of the roughed in / bad fixture, right? |
Hi @wyardley! I didn't have a chance to review. In theory you could use the same command that is used in the verify to gather the details from a "model" project/cluster, but the formatting can be tricky, so this might be simpler:
|
While terraform-google-modules#1817 added autopilot support for adding tags to `node_pool_auto_config` when `add_cluster_firewall_rules` is set to `true`, the same change did not apply for standard (non-autopilot) clusters with cluster level autoscaling (nodepool autoprovisioning) in place, Fixes terraform-google-modules#2104 Signed-off-by: William Yardley <[email protected]>
966579e
to
0b97459
Compare
/gcbrun |
Sorry, can you check if I missed something and / or anything else needs to be adjusted? |
/gcbrun |
Looks good! |
Ah, ok guess that last failure was another spurious one 🤷 thanks, glad this one is passing |
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.
Thanks for the contribution @wyardley!
While #1817 added autopilot support for adding tags to
node_pool_auto_config
whenadd_cluster_firewall_rules
is set totrue
, the same change did not apply for standard (non-autopilot) clusters with cluster level autoscaling (nodepool autoprovisioning) in place,Fixes #2104