bumping version to 0.1.1, readme update

README.md

@@ -76,6 +76,9 @@ example-node-2    tiller        tiller-deploy         140m (14%)      180m (18%)
 
 It's worth noting that utilization numbers from pods will likely not add up to the total node utilization numbers. Unlike request and limit numbers where node and cluster level numbers represent a sum of pod values, node metrics come directly from metrics-server and will likely include other forms of resource utilization.
 
+## Kubernetes Configuration
+If a `KUBECONFIG` environment variable is specified, rbac-lookup will attempt to use the config at that path, otherwise it will default to `~/.kube/config`.
+
 ## Similar Projects
 There are already some great projects out there that have similar goals.
 

pkg/capacity/resources.go

@@ -110,9 +110,9 @@ func resourceString(actual, allocatable resource.Quantity, resourceType string)
 	if allocatable.MilliValue() > 0 {
 		utilPercent = float64(actual.MilliValue()) / float64(allocatable.MilliValue()) * 100
 	}
+
 	if resourceType == "cpu" {
 		return fmt.Sprintf("%dm (%d%%)", actual.MilliValue(), int64(utilPercent))
-	} else {
-		return fmt.Sprintf("%dMi (%d%%)", actual.Value()/1048576, int64(utilPercent))
 	}
+	return fmt.Sprintf("%dMi (%d%%)", actual.Value()/1048576, int64(utilPercent))
 }

pkg/cmd/version.go

@@ -28,6 +28,6 @@ var versionCmd = &cobra.Command{
 	Use:   "version",
 	Short: "Print the version number of kube-capacity",
 	Run: func(cmd *cobra.Command, args []string) {
-		fmt.Println("kube-capacity version 0.1.0")
+		fmt.Println("kube-capacity version 0.1.1")
 	},
 }