Table: kubernetes_limit_range - Query Kubernetes Limit Ranges using SQL
Kubernetes Limit Range is a policy to constrain resource allocation (CPU, memory, etc.) in a namespace. It configures the minimum and maximum compute resources that are allowed for different types of Kubernetes objects (Pod, Container, PersistentVolumeClaim, etc.). It helps to control the resource consumption and ensure the efficient use of resources across all Pods and Containers in a namespace.
A LimitRange provides constraints that can:
- Enforce minimum and maximum compute resources usage per Pod or Container in a namespace.
- Enforce minimum and maximum storage request per PersistentVolumeClaim in a namespace.
- Enforce a ratio between request and limit for a resource in a namespace.
- Set default request/limit for compute resources in a namespace and automatically inject them to Containers at runtime.
Table Usage Guide
The kubernetes_limit_range
table provides insights into the limit ranges within Kubernetes. As a DevOps engineer, explore limit range-specific details through this table, including the types of resources being constrained, their minimum and maximum values, and the namespace in which they are applied. Utilize it to manage and optimize resource allocation across all Pods and Containers in a namespace.
Examples
Basic Info
Explore which resources have specific limits within your Kubernetes environment. This can help you manage resources effectively by understanding their configurations and creation times.
select name, namespace, resource_version, creation_timestamp, jsonb_pretty(spec_limits) as spec_limitsfrom kubernetes_limit_rangeorder by namespace;
select name, namespace, resource_version, creation_timestamp, spec_limitsfrom kubernetes_limit_rangeorder by namespace;
Get spec limits details of limit range
Assess the elements within your Kubernetes limit range to understand the specifics of each limit type, including their default values and requests. This allows you to manage resource consumption effectively by identifying the parameters that define the minimum and maximum resource usage.
select name, namespace, limits ->> 'type' as type, limits ->> 'default' as default, limits ->> 'defaultRequest' as default_requestfrom kubernetes_limit_range, jsonb_array_elements(spec_limits) as limits;
select name, namespace, json_extract(limits.value, '$.type') as type, json_extract(limits.value, '$.default') as default, json_extract(limits.value, '$.defaultRequest') as default_requestfrom kubernetes_limit_range, json_each(spec_limits) as limits;
List manifest resources
Explore the specific limits set for resources in different namespaces of a Kubernetes cluster. This can help in managing resource allocation and ensuring optimal performance.
select name, namespace, resource_version, jsonb_pretty(spec_limits) as spec_limits, pathfrom kubernetes_limit_rangewhere path is not nullorder by namespace;
select name, namespace, resource_version, spec_limits, pathfrom kubernetes_limit_rangewhere path is not nullorder by namespace;
Control examples
Schema for kubernetes_limit_range
Name | Type | Operators | 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. | |
namespace | text | Namespace defines the space within which each name must be unique. | |
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. | |
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. | |
spec_limits | jsonb | List of limit range item objects that are enforced. | |
start_line | bigint | The path to the manifest file. | |
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_limit_range