how did this work without yaml quote?

/kind bug

/priority critical-urgent

/approve no-issue

/retest

how did this work without yaml quote?

Because the consumer does not care so far: https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/gci/configure-helper.sh#L2221

/test pull-kubernetes-e2e-gce

This PR is still pending approval and does not appear to be a blocker. As such, it is being removed from 1.9. If this is in error (because it does actually represent critical breakage) please escalate the priority and return it to the milestone (and approve it) within the next 24 hours. Thanks!

/priority important-soon

@eparis @jbeda @mikedanese @roberthbailey @zmerlynn - we need of of you to hit /approve no-issue for this one today or looks like it will be dropped from 1.9 per release team

@mikedanese looks like this needs your approval

/approve no-issue

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bowei, freehan, zmerlynn

Associated issue requirement bypassed by: zmerlynn

The full list of commands accepted by this bot can be found here.

/remove-priority important-soon

[MILESTONENOTIFIER] Milestone Pull Request Current

@bowei @freehan

Note: This pull request is marked as priority/critical-urgent, and must be updated every 1 day during code freeze.

Example update:

ACK.  In progress
ETA: DD/MM/YYYY
Risks: Complicated fix required

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to @fejta).

Review the full test history for this PR.

/test all [submit-queue is verifying that this PR is safe to merge]

@freehan: The following test failed, say /retest to rerun them all:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Automatic merge from submit-queue (batch tested with PRs 56599, 56824, 56918, 56967, 56959). If you want to cherry-pick this change to another branch, please follow the instructions here.