k8s-steampipe

You can query Kubernetes cluster resources using SQL by running Steampipe SQL commands against your cluster, which translates standard SQL syntax into API calls for retrieving pods, deployments, and services without complex kubectl commands.

Yes, you can use SQL to find non-running pods in a specific namespace by writing a SELECT query against the Kubernetes pod table in Steampipe, filtering by namespace and status conditions to retrieve the exact resources.

Yes, you must explicitly specify which Kubernetes cluster to query before running SQL commands, ensuring clarity and control over cluster selection and preventing accidental queries against the wrong environment.

You can authenticate to EKS clusters when querying Kubernetes resources with SQL by integrating with tools like aws-vault and yq for credential management and configuration before executing Steampipe SQL queries.

The best way to perform ad-hoc data retrieval and analysis of Kubernetes environments is using a unified SQL interface like Steampipe, which allows direct CLI access to query cluster resources without higher-level abstractions for maximum portability.

Querying Kubernetes with SQL calls the Steampipe CLI directly for maximum portability, bypassing kubectl abstractions while still integrating with kubectl configuration and tools like yq and aws-vault for authentication setup.