Table: kubernetes_endpoint_slice - Query Kubernetes Endpoint Slices using SQL
Kubernetes Endpoint Slices are a scalable and extensible way to network traffic routing. They provide a simple way to track network endpoints within a Kubernetes cluster. Endpoint Slices group network endpoints together, allowing for efficient and flexible traffic routing.
Table Usage Guide
The kubernetes_endpoint_slice
table provides insights into the Endpoint Slices within a Kubernetes cluster. As a network engineer or DevOps professional, explore Endpoint Slice-specific details through this table, including associated services, ports, and addresses. Utilize it to manage and optimize network traffic routing within your Kubernetes environment.
Examples
Basic Info
Explore the configuration of your Kubernetes environment by identifying its various endpoints, their corresponding addresses and ports. This can provide valuable insights into the network architecture and communication within your Kubernetes cluster.
select name, namespace, generate_name as endpoint_name, address_type, endpoints, portsfrom kubernetes_endpoint_slice;
select name, namespace, generate_name as endpoint_name, address_type, endpoints, portsfrom kubernetes_endpoint_slice;
Endpoint Slice IP Information
Analyze the settings to understand the IP information for endpoint slices in a Kubernetes environment. This can be beneficial in identifying potential networking issues or inconsistencies within your application's communication paths.
select name, namespace, addr, port -> 'port' as port, port ->> 'protocol' as protocolfrom kubernetes_endpoint_slice, jsonb_array_elements(endpoints) as ep, jsonb_array_elements(ep -> 'addresses') as addr, jsonb_array_elements(ports) as port;
select name, namespace, addr.value as addr, json_extract(port.value, '$.port') as port, json_extract(port.value, '$.protocol') as protocolfrom kubernetes_endpoint_slice, json_each(endpoints) as ep, json_each(json_extract(ep.value, '$.addresses')) as addr, json_each(ports) as port;
List manifest resources
Explore the various manifest resources within a Kubernetes cluster, specifically identifying those with a defined path. This can help in understanding the distribution and configuration of resources, which is vital for efficient cluster management and troubleshooting.
select name, namespace, generate_name as endpoint_name, address_type, endpoints, ports, pathfrom kubernetes_endpoint_slicewhere path is not null;
select name, namespace, generate_name as endpoint_name, address_type, endpoints, ports, pathfrom kubernetes_endpoint_slicewhere path is not null;
Schema for kubernetes_endpoint_slice
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
address_type | text | Type of address carried by this EndpointSlice. All addresses in the slice are of the same type. Supported types are IPv4, IPv6, and FQDN. | |
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. | |
endpoints | jsonb | List of unique endpoints in this slice. | |
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. | |
ports | jsonb | List of network ports exposed by each endpoint in this slice. Each port must have a unique name. When ports is empty, it indicates that there are no defined ports. | |
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. | |
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_endpoint_slice