<p>Apparently when I set a limitrange on pod/container resources in my namespace, the limitranger will check all requests for resources. According to the documentation</p>

<pre><code>If creating or updating a resource (Pod, Container, 
PersistentVolumeClaim) violates a limit range constraint,
the request to the API server will fail with HTTP status code 403 FORBIDDEN
and a message explaining the constraint that would have been violated.
</code></pre>

<p>How do I see these errors? After deploying the limitrange I use kubectl to scale down, and then back up my deployment. When I do 'get pods' I see that the new pods were not created. Performing the scale up resulted in no output apart from '[deployment name] scaled'</p>

<p>(For the record, I'm not asking how the limitrange works, just how to see these messages. The deployment is quite complicated so there are a few possible things that could be going wrong)</p>

sil
<p>in these case the errors can be found be examining the replica set tied to the deployment with the following:</p>

<pre><code>kubectl describe replicaset %name%
</code></pre>
