<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):<br>
severity,container log</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):</p>
<ul dir="auto">
<li>FEATURE REQUEST</li>
</ul>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<ul dir="auto">
<li>1.3.6</li>
</ul>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>:<br>
Google Cloud Platform</li>
<li><strong>OS</strong> (e.g. from /etc/os-release):<br>
Ubuntu14:04</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>):<br>
3.16.0-4-amd64</li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:<br>
GKE(Google Container Engine)</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
How to specify "severity" to container logs?<br>
I'm running with kubernetes on gce.<br>
And I want to specify "severity" to container logs.</p>
<p dir="auto">I know that normally the logs written to stdout got tagged with the INFO severity and logs written to stderr got tagged with the ERROR severity.</p>
<p dir="auto">I have a question.<br>
In the future, container log Will be able to specify the severity?</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
Is there any plan to specification of container log is improved, if that is I want to hear whether the planned release time.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>
<p dir="auto"><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="144290180" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/23576" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes/kubernetes/pull/23576/hovercard" href="https://github.com/kubernetes/kubernetes/pull/23576">#23576</a> added an annotation to support DNS on Route53 on AWS.  To <em>really</em> do this right, we need to think harder about how we want to evolve Service and Ingress.  In the mean time, it seems reasonable to do the same trick with GCE Cloud DNS.  add an annotation and watch DNS appear.</p>
<p dir="auto">This would be a great opportunity for a community-contributed patch, if anyone is looking for ideas.</p>