<story><title>Kubernetes SidecarContainers feature is merged</title><url>https://github.com/kubernetes/kubernetes/pull/116429</url></story><parent_chain></parent_chain><comment><author>nrmitchi</author><text>While this is a very welcome improvement in terms of functionality, I can&amp;#x27;t help by feel that the re-use of &amp;quot;restartPolicy&amp;quot; to mean something similar, but different, when used in a different context, is a very poor decision.&lt;p&gt;Kubernetes already has an issue with having a (perceived) high barrier to entry, and I&amp;#x27;m not sure that &amp;quot;restartPolicy on a container means this, unless isn&amp;#x27;t used in &lt;i&gt;this&lt;/i&gt; list of containers, in which case it means this&amp;quot;.&lt;p&gt;I would have preferred to see a separate attribute (such as `sidecar: true`), rather than overloading (and in my opinion, abusing) the existing `restartPolicy`.</text></comment>
<story><title>Kubernetes SidecarContainers feature is merged</title><url>https://github.com/kubernetes/kubernetes/pull/116429</url></story><parent_chain></parent_chain><comment><author>jauntywundrkind</author><text>On the one hand, great.&lt;p&gt;The other hand, one of the main criticisms of Kubernetes is that it has no composition or orchestration capabilities. It&amp;#x27;s great about defining pieces of state, but managing blocks of state &amp;amp; multiple things at once is left almost entirely to external tools.&lt;p&gt;The ability to compose &amp;amp;sequence multiple containers feels like a very specific example of a much broader general capability. There&amp;#x27;s bedevilling infinite complexity to trying to figure out a fully expressive state of state management system - I get why refining a couple specialized existing capabilities is the way - but it does make me a little sad to see a lack of appetite for the broader crosscutting system problem at the root here.</text></comment>