<p>Why Kubernetes API versions are like domain names, e.g. as below? What signifies networking, k8s, and io separated by dots?</p>
<pre><code>rbac.authorization.k8s.io/v1
networking.k8s.io/v1
networking.k8s.io/v1beta1
</code></pre>

myquest4 sh
<p>Kubernetes objects are organized into API groups. <code>rbac.authorization.k8s.io</code> is one of them, holding objects such as Roles, RoleBindings, ClusterRoles and ClusterRoleBindings. <code>networking.k8s.io</code> is another where we would find Ingresses, IngressClasses and NetworkPolicies.</p>
<p>Kubernetes objects are versioned, facilitating transitions in their schema. When an object's APIversion is set to <code>rbac.authorization.k8s.io/v1</code>, its description should match the v1 schema - relative to object kind (role, clusterrole, ...), in that API group.</p>
<p>You could find more about those schemas, using <code>kubectl explain &lt;object-name&gt;</code>.</p>
<p>You can list known object names and their api group, with <code>kubectl api-resources</code></p>
