Skip to main content

Installing Minishift on Windows 10 Home

Minishift is a tool to run OpenShift Origin locally as a single node cluster inside a Virtual Machine. It is a good choice for development or doing PoCs locally before deploying things in a real OpenShift cluster. In this post I am going to explain how to install and run it on a Windows 10 Home machine, where no Hyper-V support is available.
The only available alternative to Hyper-V is Oracle VirtualBox. You need to install it before going on with the Minishift installation: follow the instructions in the official website or use the Chocolatey package manager.
If you don't have Chocolatey in the destination machine, you can install it by opening an Admin PowerShell and first checking which execution policy is set, by running the Get-ExecutionPolicy command. If it returns Restricted, then install by executing:

Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))

The fastest and secure way to install Minishift is through Chocolatey as well. From an Admin PowerShell execute:

choco install -y minishift

At the end of the installation process, double check that everything was fine by executing:

minishift version

This command should print the version of the installed Minishift.
You need now to install, using Chocolatey as well, kubectl, the Kubernetes command-line tool:

choco install -y kubernetes-cli

Finally, you need to install oc, the OpenShift command-line tool (using Chocolatey of course):

choco install -y openshift-cli

Before starting the cluster, set up VirtualBox as default driver for Minishift:

minishift config set vm-driver virtualbox

You can now start Minishift:

minishift start

The first time the start would be slower as the ISO image needs to be downloaded.
Once the server is up and running, you can access the web UI at the following URL:

https://<minishift_ip>:8443/console



Login using developer as username and any value as password. I suggest to use Firefox or Chrome for the web UI.
You can also login using the oc client.
Minishift is now ready to be used. Enjoy it!

Comments

  1. What an article you have written. I really impressed because I was looking for an article about this topic. I am very happy to get your post. Thanks for this awesome and informative article. I will back again for sure.
    HVAC repair in Greer SC

    ReplyDelete
  2. TORONTO An Iranian
    Would-be medical exec from Iran barred from Canada over alleged ties to Tehran's nuclear program. Ramin Fallah was labeled a security threat because he ...
    You've visited this page many times. Last visit: 5/12/21

    ReplyDelete
  3. Nice informative content. Thanks for sharing the valuable information.
    Node Js Development
    Node Js Framework

    ReplyDelete

Post a Comment

Popular posts from this blog

Streamsets Data Collector log shipping and analysis using ElasticSearch, Kibana and... the Streamsets Data Collector

One common use case scenario for the Streamsets Data Collector (SDC) is the log shipping to some system, like ElasticSearch, for real-time analysis. To build a pipeline for this particular purpose in SDC is really simple and fast and doesn't require coding at all. For this quick tutorial I will use the SDC logs as example. The log data will be shipped to Elasticsearch and then visualized through a Kibana dashboard. Basic knowledge of SDC, Elasticsearch and Kibana is required for a better understanding of this post. These are the releases I am referring to for each system involved in this tutorial: JDK 8 Streamsets Data Collector 1.4.0 ElasticSearch 2.3.3 Kibana 4.5.1 Elasticsearch and Kibana installation You should have your Elasticsearch cluster installed and configured and a Kibana instance pointing to that cluster in order to go on with this tutorial. Please refer to the official documentation for these two products in order to complete their installation (if you do

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax: sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv where the format could be csv , json or column . Example: sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez  who was presenting Rapids , the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics. Fig. 1 - Overview of the Rapids eco-system Rapids is a suite of Open Source libraries: cuDF cuML cuGraph cuXFilter I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab , starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker. I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids. Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You