<p>We can check the service accounts in Kubernetes Cluster. Likewise, Is it possible to check the existing users and groups of my Kubernetes cluster with Cluster Admin privileges. If yes then how ? If no then why ?</p>
<p>NOTE: I am using EKS</p>

Aman
<p>Posting this as a community wiki, feel free to edit and expand.</p>
<hr />
<p>This won't answer everything, however there are some concepts and ideas.</p>
<p>In short words there's no easy way. It's not possible to do using kubernetes itself. Reason for this is:</p>
<blockquote>
<p>All Kubernetes clusters have two categories of users: service accounts
managed by Kubernetes, and normal users.</p>
<p>It is assumed that a cluster-independent service manages normal users
in the following ways:</p>
<ul>
<li>an administrator distributing private keys</li>
<li>a user store like Keystone or Google Accounts</li>
<li>a file with a list of usernames and passwords</li>
</ul>
<p>In this regard, Kubernetes does not have objects which represent normal
user accounts. Normal users cannot be added to a cluster through an
API call.</p>
</blockquote>
<p><a href="https://kubernetes.io/docs/reference/access-authn-authz/authentication/#users-in-kubernetes" rel="nofollow noreferrer">Source</a></p>
<p><a href="https://stackoverflow.com/questions/51612976/how-to-view-members-of-subject-with-group-kind">More details and examples from another answer on SO</a></p>
<hr />
<p>As for EKS part which is mentioned, it should be done using AWS IAM in connection to kubernetes RBAC. Below articles about setting up IAM roles in kubernetes cluster. Same way it will be possible to find which role has <code>cluster admin</code> permissions:</p>
<ul>
<li><a href="https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html" rel="nofollow noreferrer">Managing users or IAM roles for your cluster</a></li>
<li><a href="https://aws.amazon.com/premiumsupport/knowledge-center/amazon-eks-cluster-access/" rel="nofollow noreferrer">provide access to other IAM users and roles</a></li>
</ul>
<p>If another tool is used for identity managing, it should be used (e.g. LDAP)</p>
