Run OpenShift locally.
Minishift’s goal is to become the default choice for running a single-node OpenShift cluster on your local host. Either for evaluation purposes or for ongoing development.
Due to the fact that Minishift builds on OpenShift cluster up, Minishift’s focus lies on providing more value to the basic cluster up provisioning. This includes virtual machine creation and management, making it easier to configure OpenShift in precisely the way you want and providing useful shortcut commands for making your work easier.
The Minishift team currently uses the GitHub issue tracker to plan its work. Issues are generally categorized into tasks, bugs and features. Looking at the latter, features, is probably the best way to get an overview where Minishift is heading.
The following sections give a high level overview of the envisioned features and how they fit into upcoming releases. Of course this is subject to change and actual version names might change as well, because semantic versioning is used to determine the final version name of a given release.
-
✓ Ability to select the OpenShift version of the cluster #141
-
✓ HTTP Proxy Support #90
-
✓ Exposure of the OpenShift registry #254
-
✓ Ability to configure/patch OpenShift’s master and node configuration #276
-
✓ Ability to customize cluster (for example, adding templates and imagestreams) #177
-
✓ Add 'minishift' context #359
-
✓ Enable ability to use persistent volumes #389
-
✓ Add update command #72
-
✓ Implement caching of OpenShift image #143
-
✓ Incorporate NodePort into minishift openshift service #1106
-
❏ Ability to create and manage multiple clusters #126