v0.0.3

# Print resource usage report to terminal
resource-calculator calculate --apiGroups=kubedb.com

# Print resource usage report to json
resource-calculator calculate --apiGroups=kubedb.com -o json > report.json


# Print resource usage report to terminal for all cluster contexts found in KUBECONFIG
resource-calculator calculate --apiGroups=kubedb.com --all

# Print resource usage report to json for all cluster contexts found in KUBECONFIG
resource-calculator calculate --apiGroups=kubedb.com --all -o json > report.json

resource-calculator uses the same library as kubectl internally. So, by default it will be the default context in your ~/.kube/config file or KUBECONFIG environment variable, if set. To try with different clusters in your kubeconfig file, you can pass the --context flag.

v0.0.2

# Print resource usage report to terminal
resource-calculator calculate --apiGroups=kubedb.com

# Print resource usage report to json
resource-calculator calculate --apiGroups=kubedb.com -o json > report.json


# Print resource usage report to terminal for all cluster contexts found in KUBECONFIG
resource-calculator calculate --apiGroups=kubedb.com --all

# Print resource usage report to json for all cluster contexts found in KUBECONFIG
resource-calculator calculate --apiGroups=kubedb.com --all -o json > report.json

resource-calculator uses the same library as kubectl internally. So, by default it will be the default context in your ~/.kube/config file or KUBECONFIG environment variable, if set. To try with different clusters in your kubeconfig file, you can pass the --context flag.

v0.0.1

resource-calculator calculate --apiGroups=kubedb.com

resource-calculator uses the same library as kubectl internally. So, by default it will be the default context in your ~/.kube/config file or KUBECONFIG environment variable, if set. To try with different clusters in your kubeconfig file, you can pass the --context variable.