Table: kubernetes_cluster_role_binding - Query Kubernetes Cluster Role Bindings using SQL

A Kubernetes Cluster Role Binding binds a role to subjects. Subjects can be groups, users, or service accounts. Cluster Role Binding grants permissions to users at the cluster level, which includes all namespaces.

Table Usage Guide

The kubernetes_cluster_role_binding table provides insights into Cluster Role Bindings within Kubernetes. As a DevOps engineer, explore binding-specific details through this table, including subjects, role references, and associated metadata. Utilize it to uncover information about bindings, such as the roles binded to specific subjects, the namespaces of the roles, and the verification of role references.

Examples

Basic Info

Explore which roles are bound to different subjects in your Kubernetes cluster. This allows you to gain insights into the permissions and access levels within your system, assisting in managing security and access control.

select
  name,
  role_name,
  role_kind,
  jsonb_pretty(subjects) as subjects,
  creation_timestamp
from
  kubernetes_cluster_role_binding
order by
  name;

select
  name,
  role_name,
  role_kind,
  subjects,
  creation_timestamp
from
  kubernetes_cluster_role_binding
order by
  name;

Get details subject and role details for bindings

Uncover the details of role bindings within a Kubernetes cluster. This query is particularly useful for administrators who want to keep track of roles and associated subjects in a systematic order, thereby facilitating efficient management of access and permissions within the cluster.

select
  name as binding_name,
  role_name,
  subject ->> 'name' as subject_name,
  subject ->> 'namespace' as subject_namespace,
  subject ->> 'apiGroup' as subject_api_group,
  subject ->> 'kind' as subject_kind
from
  kubernetes_cluster_role_binding,
  jsonb_array_elements(subjects) as subject
order by
  role_name,
  subject_name;

select
  name as binding_name,
  role_name,
  json_extract(subject.value, '$.name') as subject_name,
  json_extract(subject.value, '$.namespace') as subject_namespace,
  json_extract(subject.value, '$.apiGroup') as subject_api_group,
  json_extract(subject.value, '$.kind') as subject_kind
from
  kubernetes_cluster_role_binding,
  json_each(subjects) as subject
order by
  role_name,
  subject_name;

Get cluster role bindings associated for each role

Discover the segments that have specific role bindings in a Kubernetes cluster, which can aid in understanding the distribution and assignment of roles across the cluster. This can be particularly useful for managing permissions and access controls within the system.

select
  role_name,
  jsonb_agg(name) as bindings
from
  kubernetes_cluster_role_binding
group by
  role_name;

select
  role_name,
  json_group_array(name) as bindings
from
  kubernetes_cluster_role_binding
group by
  role_name;

List manifest resources

Assess the elements within your Kubernetes cluster to understand the relationship and permissions between different roles and resources. This allows you to maintain a secure and well-organized system by identifying any irregularities or potential vulnerabilities in role assignments.

select
  name,
  role_name,
  role_kind,
  jsonb_pretty(subjects) as subjects,
  path
from
  kubernetes_cluster_role_binding
where
  path is not null
order by
  name;

select
  name,
  role_name,
  role_kind,
  subjects,
  path
from
  kubernetes_cluster_role_binding
where
  path is not null
order by
  name;

Query examples

Control examples

All Controls > Cluster Role Binding > ClusterRoleBinding subjects should not actively use default service accounts

Schema for kubernetes_cluster_role_binding

Name	Type	Description
_ctx	jsonb	Steampipe context in JSON form.
annotations	jsonb	Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata.
context_name	text	Kubectl config context name.
creation_timestamp	timestamp with time zone	CreationTimestamp is a timestamp representing the server time when this object was created.
deletion_grace_period_seconds	bigint	Number of seconds allowed for this object to gracefully terminate before it will be removed from the system. Only set when deletionTimestamp is also set.
deletion_timestamp	timestamp with time zone	DeletionTimestamp is RFC 3339 date and time at which this resource will be deleted.
end_line	bigint	The path to the manifest file.
finalizers	jsonb	Must be empty before the object is deleted from the registry. Each entry is an identifier for the responsible component that will remove the entry from the list. If the deletionTimestamp of the object is non-nil, entries in this list can only be removed.
generate_name	text	GenerateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided.
generation	bigint	A sequence number representing a specific generation of the desired state.
labels	jsonb	Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services.
name	text	Name of the object. Name must be unique within a namespace.
owner_references	jsonb	List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.
path	text	The path to the manifest file.
resource_version	text	An opaque value that represents the internal version of this object that can be used by clients to determine when objects have changed.
role_api_group	text	The group for the referenced role.
role_kind	text	Type of the role refrenced must be one of ClusterRole or Role.
role_name	text	Name of the cluster role for which access is granted to subjects.
source_type	text	The source of the resource. Possible values are: deployed and manifest. If the resource is fetched from the spec file the value will be manifest.
sp_connection_name	text	Steampipe connection name.
sp_ctx	jsonb	Steampipe context in JSON form.
start_line	bigint	The path to the manifest file.
subjects	jsonb	List of references to the objects the role applies to.
tags	jsonb	A map of tags for the resource. This includes both labels and annotations.
title	text	Title of the resource.
uid	text	UID is the unique in time and space value for this object.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- kubernetes

You can pass the configuration to the command with the --config argument:

steampipe_export_kubernetes --config '<your_config>' kubernetes_cluster_role_binding