Kubernetes API Reference Python API Docs | dltHub
Build a Kubernetes API Reference-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Kubernetes API is the REST API served by a Kubernetes cluster to manage and inspect cluster resources. The REST API base URL is Cluster-specific API base URLs (examples): - Core group: https://<kubernetes-api-server-host>/api/v1 - Named groups: https://<kubernetes-api-server-host>/apis/<group>/<version> - Discovery: https://<kubernetes-api-server-host>/api and https://<kubernetes-api-server-host>/apis - OpenAPI: https://<kubernetes-api-server-host>/openapi/v3 and All requests require cluster-authenticated credentials (e.g., Bearer token or client certificate)..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Kubernetes API Reference data in under 10 minutes.
What data can I load from Kubernetes API Reference?
Here are some of the endpoints you can load from Kubernetes API Reference:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| pods | /api/v1/namespaces/{namespace}/pods | GET | items | List Pods in a namespace |
| pods_all_namespaces | /api/v1/pods | GET | items | List Pods across all namespaces |
| services | /api/v1/namespaces/{namespace}/services | GET | items | List Services in a namespace |
| deployments | /apis/apps/v1/namespaces/{namespace}/deployments | GET | items | List Deployments in a namespace |
| jobs | /apis/batch/v1/namespaces/{namespace}/jobs | GET | items | List Jobs in a namespace |
| namespaces | /api/v1/namespaces | GET | items | List Namespaces |
| nodes | /api/v1/nodes | GET | items | List Nodes |
| discovery_api | /api and /apis | GET | (response contains groups/versions; resources lists under group documents) | Discovery endpoints listing API groups and resources |
| openapi | /openapi/v3 | GET | (OpenAPI JSON) | OpenAPI v3 specification for group/version schemas |
How do I authenticate with the Kubernetes API Reference API?
Kubernetes API accepts client authentication via TLS client certificates, bearer tokens (Authorization: Bearer ), and other pluggable mechanisms. Typical client setups use a kubeconfig file with a token or client-certificate and CA; include Authorization and/or present TLS client certs when connecting to the API server.
1. Get your credentials
- Obtain kubeconfig access from cluster administrator or cloud provider (e.g., EKS/GKE/AKS) which contains user credentials.
- For a service account token: create a ServiceAccount and bind appropriate RBAC; then read the token from the secret mounted for that service account (or use kubectl -n get secret -o jsonpath='{.data.token}' | base64 -d).
- For user tokens: use cloud provider IAM to create or retrieve kubeconfig credentials (e.g., gcloud, aws eks update-kubeconfig).
- Use the token or client-certificate/CA from kubeconfig when configuring dlt source.
2. Add them to .dlt/secrets.toml
[sources.kubernetes_api_reference_source] token = "your_service_account_token_here" api_server = "https://your.k8s.api.server:6443" ca_cert_path = "/path/to/ca.crt" # optional if using TLS verification
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Kubernetes API Reference API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python kubernetes_api_reference_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline kubernetes_api_reference_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset kubernetes_api_reference_data The duckdb destination used duckdb:/kubernetes_api_reference.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline kubernetes_api_reference_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads pods and services from the Kubernetes API Reference API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def kubernetes_api_reference_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "Cluster-specific API base URLs (examples): - Core group: https://<kubernetes-api-server-host>/api/v1 - Named groups: https://<kubernetes-api-server-host>/apis/<group>/<version> - Discovery: https://<kubernetes-api-server-host>/api and https://<kubernetes-api-server-host>/apis - OpenAPI: https://<kubernetes-api-server-host>/openapi/v3", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "pods", "endpoint": {"path": "api/v1/namespaces/{namespace}/pods", "data_selector": "items"}}, {"name": "services", "endpoint": {"path": "api/v1/namespaces/{namespace}/services", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="kubernetes_api_reference_pipeline", destination="duckdb", dataset_name="kubernetes_api_reference_data", ) load_info = pipeline.run(kubernetes_api_reference_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("kubernetes_api_reference_pipeline").dataset() sessions_df = data.pods.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM kubernetes_api_reference_data.pods LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("kubernetes_api_reference_pipeline").dataset() data.pods.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Kubernetes API Reference data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Troubleshooting
Authentication failures
If you receive 401 Unauthorized or 403 Forbidden, verify the token or client certificate used. Ensure the token is valid, not expired, and the Kubernetes RBAC grants the requested read permissions to the target resource and namespace.
Rate limits and throttling
Kubernetes API server may enforce rate limiting on clients; 429 Too Many Requests can be returned. Implement exponential backoff and retries for 429 and 5xx errors.
Pagination
Some list endpoints support limit and continue query parameters for pagination. Use ?limit= and the returned metadata.continue value to page through lists until continue is empty.
Discovery and versioning quirks
API paths vary by API group/version; use /api and /apis discovery endpoints or the cluster OpenAPI (/openapi/v3) to enumerate available group versions and resource paths for the target cluster.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Kubernetes API Reference?
Request dlt skills, commands, AGENT.md files, and AI-native context.