Is this a request for help (If yes, you should instead post it in StackOverflow, Slack channel, or mailing list, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one (If you found any duplicates, you should instead reply there or use the 👍 icon in the upper-right of the issue message):

Is this a BUG REPORT or FEATURE REQUEST (choose one):

Kubernetes version (use kubectl version):

Environment:

• Cloud provider:
• OS:
• kernel:
• Install tools:
• Others:

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else do we need to know:

What this PR does / why we need it:

Which issue this PR fixes (optional, in fixes #<issue number>(, #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Release note:

* Enter your extended release note here (newlines are formatted as bullets).  If this PR does not warrant a release
  note, just say `NONE`.
-OR-
* Use the release-note-* labels to set the release note state (if you have access)
* Clear this block to use the PR title as the release note

The above is how current issue & PR template looks, major changes include:

• Addressed all comments in previous PR Add an issue template, tighten PR template #28488
• Make it shorter (so people will read it)
• Removed PLEASE REMOVE THIS COMMENT BLOCK BEFORE SUBMITTING (it won't display anyways so let's save this space)
• Made all "read this and that paragraph" more Q&A-ish (so people can't ignore it)

@bgrant0607 ptal

Overall this LGTM.

All comments addressed, @philips @bgrant0607 ptal

LGTM

Squashed; applying tag

GCE e2e build/test passed for commit de91512.

• Test Results
• Build Log
• Test Artifacts
• Internal Jenkins Results

Automatic merge from submit-queue