kubewise helps you see the cost impact of planned Kubernetes changes before you make them. It takes a snapshot of your cluster, then shows how changes may affect cost and risk.
Use it to compare plans like:
- right-sizing workloads
- moving pods to spot instances
- consolidating nodes
- testing cost changes before rollout
It works as a kubectl plugin through krew, so it fits into a common Kubernetes workflow.
Before you install kubewise, make sure you have:
- a Windows computer
- internet access
- permission to download files from GitHub
- kubectl installed
- krew installed if you want to use the kubectl plugin flow
- access to a Kubernetes cluster if you plan to snapshot live data
If you only want to open the app and explore local snapshots, you still need a Windows system and the release file from GitHub.
Visit this page to download:
On that page:
- open the latest release
- find the Windows file
- download the file to your computer
- save it in a folder you can find again, such as Downloads
If the release contains a zip file, extract it first before you run the app.
After the file finishes downloading:
- open File Explorer
- go to the folder with the download
- if the file is zipped, right-click it and choose Extract All
- open the extracted folder
- look for the kubewise file or installer
- double-click the file to run it
If Windows shows a security prompt:
- choose More info
- choose Run anyway if you trust the source
- wait for the app to open
If the release includes a command-line file, keep it in a folder you can reach from Command Prompt or PowerShell.
kubewise also works as a kubectl plugin through krew.
If you already use krew:
- open PowerShell
- make sure kubectl works on your machine
- install the kubewise plugin from the krew index, if the release provides that path
- run it from kubectl like other plugins
A common plugin flow looks like this:
- open a terminal
- run a kubectl command
- use the kubewise command from the plugin name
- connect it to your cluster snapshot or plan file
If you do not use krew, you can still use the release download from GitHub.
When kubewise opens for the first time, it may ask for:
- a cluster context
- a snapshot target
- a file location for saved plans
- access to Kubernetes resources
A simple first run looks like this:
- open kubewise
- choose your cluster
- create a snapshot
- review the current cost view
- try one change at a time
- compare the cost result before and after
Start with one small change so the results are easy to read.
kubewise is useful when you want to compare the effect of a change before you apply it.
Common checks include:
- right-sizing pods that use too much CPU or memory
- moving workloads from on-demand nodes to spot instances
- combining small nodes into fewer larger nodes
- reviewing cost shifts after a planned rollout
- checking the risk of a change before approval
It gives you a way to look at both cost and risk in one place.
A simple kubewise workflow is:
- snapshot your cluster
- model a change
- compare the expected cost
- review the risk impact
- apply the change if the result looks good
This helps you avoid trial and error in the live cluster.
Use kubewise when you want to:
- prepare a cost review for a Kubernetes team
- check whether spot migration is worth it
- see if node consolidation lowers spend
- test a new sizing plan before deployment
- support finops work with cluster data
- share a clear view of cost impact with non-technical people
- use a fresh snapshot
- compare one change at a time
- keep cluster names and node groups clear
- review both cost and risk, not cost alone
- save your plan files so you can compare later
- use the same context each time when possible
If kubewise does not open:
- check that the download finished
- make sure you extracted the zip file
- right-click the file and try Run as administrator
- confirm Windows did not block the file
If kubectl or krew does not work:
- open PowerShell
- type
kubectl version - confirm kubectl is installed
- confirm your cluster context is set
- check that krew is on your PATH if you use the plugin flow
If the app cannot read cluster data:
- confirm you are signed in to the right cluster
- check your access rights
- try again with a different context
- use a snapshot created from a cluster you can reach
The release page may include files such as:
- a Windows zip package
- a Windows executable
- a plugin package for krew
- release notes
- checksum files
Choose the Windows file that matches the way you want to use kubewise.
kubewise works with cluster data, so it may need read access to Kubernetes resources. Use an account that can view the parts of the cluster you want to model. Keep the download from the official GitHub release page so you know where the file came from.
If you want the simplest path on Windows:
- go to the release page
- download the Windows file
- extract it if needed
- open the app
- create a snapshot
- review the cost plan
- keep the file in a known folder for later use
To get the latest version, check the releases page again:
Look for newer release notes, newer Windows files, and any changes to the plugin install steps
If you are new to this tool, use this path:
- download kubewise from the releases page
- open the file on Windows
- connect it to your cluster or load a snapshot
- choose one possible change
- review the cost result
- review the risk result
- save the plan for later review