Integrations
Use Helm, Argo, Prometheus, OTel, Grafana, Tekton, KEDA, Istio, Crossplane, and GitOps through detected tools and real APIs.
kprompt orchestrates integrations; it does not replace them. Run kprompt tools to see what is installed or configured. Missing Helm / Argo / Prometheus can be planned with kprompt setup (approve-gated). Mutating operations still pass through plan, safety, and approval.
kprompt tools
kprompt setup --dry-runGeneric Kubernetes reads
Get/list any discoverable built-in or CRD via discovery and the dynamic client. Cluster-scoped resources (Node) ignore namespace; Secrets use the same table path (type + key count). Authorization is your kubeconfig RBAC.
kprompt "how many nodes are in the cluster"
kprompt "list configmaps" -n default
kprompt "list widgets.example.com" -n demoHelm
Install and upgrade plans call the Helm CLI and surface template/dry-run previews. Helm must be available on PATH. Uninstall remains wipe-class and receives stricter safety treatment.
kprompt "install redis" -n cache
kprompt "upgrade prometheus chart" -n monitoringArgo Workflows
kprompt detects the Workflow CRD, generates a reviewable manifest, submits it with the Kubernetes dynamic client, and can report or wait for terminal status.
kprompt "train a yolov11 model"
kprompt "train a yolov11 model" --approve --wait
kprompt "get workflow train-yolov11"Prometheus
Performance explain is read-only. It uses bounded instant/range queries to inspect CPU, memory, p95 latency, replica, and HPA signals for a workload.
kprompt config set tools.prometheus.url http://prometheus.monitoring:9090
kprompt "why is my api slow?" -n productionOpenTelemetry (Jaeger / Tempo)
Trace intents search the configured Jaeger or Tempo backend, print a span tree, and narrate bottleneck spans when present. Deep dive: kprompt + OpenTelemetry.
kprompt config set tools.otel.endpoint http://tempo.monitoring:3200
kprompt config set tools.otel.backend tempo
kprompt "trace payment request"Grafana
Dashboard intents search Grafana and summarize panel metadata (read-only). Configure URL and API token via tools.grafana.* or environment variables.
kprompt config set tools.grafana.url https://grafana.example
kprompt "show payments dashboard"Optimize & service graph
Optimize is a read-only cluster report (idle workloads, rightsizing, HPA hints). Optional follow-up scale/patch plans still require their own approval. Service graphs build from Kubernetes Services/Endpoints and can add OTel call edges when configured. Walkthrough: optimize my cluster.
kprompt "optimize my cluster"
kprompt "show service dependency graph"
kprompt "show service dependency graph for payments"Tekton
Tekton PipelineRuns generate as reviewable CRs before submit. Missing Tekton CRDs fail clear — kprompt does not invent a pipeline engine.
kprompt "run the build pipeline"
kprompt "create a CI pipeline"KEDA
Event-driven scale and scale-to-zero map to KEDA ScaledObjects. The CR is planned first; apply still needs approval.
kprompt "autoscale api with KEDA to zero when idle"Istio
Istio is read-first: VirtualService traffic and canary summaries. kprompt does not claim write canaries or mesh install.
kprompt "show traffic for checkout"
kprompt "show virtualservice for payments"Crossplane
Cloud claims via Crossplane CRDs are RiskHigh and need strong approval. Prefer an existing claim over inventing a cloud account.
kprompt "provision a postgres database"GitOps (Flux / Argo CD)
Status and health are read-only. Sync / promote / rollback paths require approval and apply through the real Flux Kustomization or Argo CD Application APIs. Deep dive: kprompt + Argo CD.
kprompt "show gitops sync status"
kprompt "sync the payments application" --approveMulti-tool routes
Chain steps across backends with then / and then. Mutating chains show one aggregate plan and ask for a single approval.
kprompt "why is api slow then scale api to 4"
kprompt "show gitops sync status then sync payments" --approve