<p>What is the difference between Objects and Resouces in Kubernetes world? </p>

<p>I couldn't find it from <a href="https://kubernetes.io/docs/concepts/" rel="noreferrer">https://kubernetes.io/docs/concepts/</a> . I wonder they make no distinction about them but seems they see objects as a high-level concept of resources. </p>

<p>A representation of a specific group+version+kind is an object. For example, a v1 Pod, or an apps/v1 Deployment. Those definitions can exist in manifest files, or be obtained from the apiserver.</p>

<p>A specific URL used to obtain the object is a resource. For example, a list of v1 Pod objects can be obtained from the <code>/api/v1/pods</code> resource. A specific v1 Pod object can be obtained from the <code>/api/v1/namespaces/&lt;namespace-name&gt;/pods/&lt;pod-name&gt;</code> resource.</p>

<p>API discovery documents (like the one published at /api/v1) can be used to determine the resources that correspond to each object type.</p>

<p>Often, the same object can be retrieved from and submitted to multiple resources. For example, v1 Pod objects can be submitted to the following resource URLs:</p>

<ol>
<li><code>/api/v1/namespaces/&lt;namespace-name&gt;/pods/&lt;pod-name&gt;</code></li>
<li><code>/api/v1/namespaces/&lt;namespace-name&gt;/pods/&lt;pod-name&gt;/status</code></li>
</ol>

<p>Distinct resources allow for different server-side behavior and access control. The first URL only allows updating parts of the pod spec and metadata. The second URL only allows updating the pod status, and access is typically only given to kubelets.</p>

<p>Authorization rules are based on the resources for particular requests.</p>
