Upstream software project

kubectl-cost

CLI for determining the cost of Kubernetes workloads

About kubectl-cost

CLI for determining the cost of Kubernetes workloads

This project links 4 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

kubectl-cost repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Tumbleweed: 4 package records. Catalog coverage diagram, not an application screenshot.kubectl-cost: recorded package coverageopenSUSE Tumbleweed4 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
kubectl-cost
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

kubectl-cost is a kubectl plugin that provides easy CLI access to Kubernetes cost information, like historical cost and predicted future cost, via Kubecost's APIs. It allows developers, devops, and others to quickly determine the cost & efficiency of any Kubernetes workload.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Tumbleweed

  1. Package kubectl-cost

    tumbleweed (openSUSE Tumbleweed) (Unspecified): CLI for determining the cost of Kubernetes workloads

    0.6.6-1.9: x86_64

    Source: kubectl-cost

  2. Source: kubectl-cost

  3. Source: kubectl-cost

  4. Source: kubectl-cost

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.