Happy holidays and seasonal greetings. Although many of you celebrate
Christmas, some elves have remained hard at work to be able to deliver
you the release of Minishift 1.29.0.
Minishift  is a command-line tool that provisions and manages a
single-node OpenShift cluster. You can run Minishift on GNU/Linux,
Microsoft Windows, or macOS.
In version 1.29.0, we added new features, enhancements, and bug fixes including:
* Minishift delete command now also clear the kubeconfig entry which
created by it.
* Minishift setup command now have support for Mac OS (Give it a try).
* Mutating and validating webhooks are now part of minishift addons
and can be enabled.
You can find a detailed list of issues in the release notes .
For information about getting started, using, and developing
Minishift, see the documentation .
Please try the new release. The easiest upgrade path is by simply running:
$ minishift update
We are looking forward to your feedback. The Minishift community 
hangs out in the #minishift channel on Freenode and it is the perfect
place to discuss anything Minishift related.
You can sign up for our mailing list  to receive development
updates, ask questions about Minishift, suggest ideas, and talk to the
I might change networks more often than underwear.
And those networks are often in various indecently countries, often in
hotels and conference centers/meeting rooms.
And one thing that I have seen lately is that commands like "minishift ip"
become really, really slow.
This is problematic because I use "minishift ip" in my scripts for curling
my NodePort-based (or Route-based) Service.
What theories do you all have as it relates to that command?
I have installed Grafana minishift add-ons running on windows laptop, when i import the json file to create dashboard, it do not show any of the panel, where as if i create new graph panel its able to show the graphs. the json file was created from grafana image 5.3.4 version.
Yesterday while facing issues with the system tray release job in
circle ci, i had to remove the
MINISHIFT_GITHUB_API_TOKEN env variable.
There's already an env variable GITHUB_TOKEN with scope of repo, which
can be used instead,
it seems having two tokens as env variables somehow makes the
uploading of bits to Github
release fail, could be some issue in the github-release  program.
Apologies for removing it without informing first and breaking any
scripts/jobs that relied on it.