Change:
As of 164.0.0 (2017-07-26), the and flags are deprecated from a number of calls: We use these pretty extensively in our cluster scripts, and we need to update them to use so they don't mysteriously break in the future.
I'd like to take a look at this. It is my first kubernetes bug, so please let me know if there's anything I need to do apart from opening a PR referencing this issue number.
Welcome! That should be all you need to do. I'd assign this issue to you, but GitHub doesn't allow assigning to non-org members, so your comment will have to suffice.
Also leaving as a note: it looks like deprecates and for: These don't appear to be used in the codebase, but worth noting for future reference.
Please note that any of the changes need to be cherry-picked to earlier release branches also. Otherwise presubmit tests will fail for PRs on those branches (unless you skip e2e tests for those branches which I don't think we want).
I think this issue is becoming increasingly important, as I've been asked by at least 3 people by now why the kube-up/kube-down scripts are failing. Could someone make sure it's fixed asap?
gcloud 168.0.0 seems to have broken things further. I'm now consistently getting stuff like
Yes.. Heard the same issue from too very recently. The fix needs to go in asap.
this latest breakage seems different. is now returning a URL, and isn't parsing that URL correctly.
fyi -
This is being worked on by in
Cherry pick PRs are and
There's at least one call we missed because it used instead of : Frustrating, but an easy fix.
[MILESTONENOTIFIER] Milestone Labels Complete Issue label settings: sig/cluster-lifecycle: Issue will be escalated to these SIGs if needed. priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts. kind/cleanup: Adding tests, refactoring, fixing old bugs. <detailsAdditional instructions available <a href=""here</aThe commands available for adding these labels are documented <a href=""here</a</details
Wonderful. Sorry we missed that one.
Everything is terrible. Now we're getting warning messages like
Had a quick look, the change was introduced in 168.0.0.0 (although there's nothing in the release notes!). and is now only allowed an optional trailing --filter=(metadata.created-by~'.zones(..)'` should fix it, but I won't get a chance to test until the weekend.
says that this issue is not a release blocker for 1.8, but that we will need to backport the fix into the 1.8 release branch.
- I'm going to bump this out of the 1.8 milestone as it isn't a release blocking issue, but we shouldn't lose track of fixing it.
Thanks
A new arrival in my family has meant I've not had time to get make a PR for this, if it's still here when I have some time I'll take it. But if anyone else has the capacity, or if you're reading this and looking for a good first issue to take, please comment below!
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
is this still relevant?
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten /remove-lifecycle stale
I don't see any gcloud warnings (of this form) in https://k8s-, so I think we're good for now. /close

Discussion:
# # $1: project function get-template() { <del> gcloud compute instance-templates list -r "${NODE_INSTANCE_PREFIX}-template(-(${KUBE_RELEASE_VERSION_DASHED_REGEX}|${KUBE_CI_VERSION_DASHED_REGEX}))?"  </del> <ins> gcloud compute instance-templates list  --filter="name ~ '${NODE_INSTANCE_PREFIX}-template(-(${KUBE_RELEASE_VERSION_DASHED_REGEX}|${KUBE_CI_VERSION_DASHED_REGEX}))?'"  </ins> --project="${1}" --format='value(name)' }