For the best local developer experience on Kubernetes and OpenShift fabric8 recommends minikube and minishift
Here is a video walking you through these steps
Now clone the fabric8 installer git repository repository and type these commands:
$ git clone https://github.com/fabric8io/fabric8-installer.git $ cd fabric8-installer/vagrant/openshift
Depending on your host operating system you need to install an additional vagrant plugin:
vagrant plugin install landrushfor Linux and OS X
vagrant plugin install vagrant-hostmanagerfor Windows
The next steps are needed for proper routing from the host to OpenShift services which are exposed via routes:
Linux: Setup a
dnsmasq DNS proxy locally. The detailed
procedure depends on the Linux distribution used. Here is the
example for Ubuntu:
sudo apt-get install -y resolvconf dnsmasq sudo sh -c 'echo "server=/vagrant.f8/127.0.0.1#10053" > /etc/dnsmasq.d/vagrant-landrush' sudo service dnsmasq restart
Windows: Unfortunately for Windows no automatic routing for new
services is possible. You have to add new routes manually to
%WINDIR%\System32\drivers\etc\hosts. For your convenience, a set
of routes for default Fabric8 applications has been pre-added. For
new services look for the following line and add your new routes
<service-name>.vagrant.f8) to this file on a new line like this:
## vagrant-hostmanager-start id: 9a4ba3f3-f5e4-4ad4-9e80-b4045c6cf2fc 172.28.128.4 vagrant.f8 fabric8.vagrant.f8 jenkins.vagrant.f8 ..... 172.28.128.4 myservice.vagrant.f8 ## vagrant-hostmanager-end
OS X: Nothing has to be done. OS X will automatically resolve
all routes to
*.vagrant.f8 to your Vagrant VM. This is done via OS
X's resolver feature (see
man 5 resolver for details).
Now startup the Vagrant VM.
Note the vagrant image is by default configured with 2 CPU cores and
4 gigs of memory. It is recommended to not exceed about half of your
machine’s resources. In case you have plenty of resources on your
machine you can increase the settings by editing the
Vagrantfile. The settings are defined in the bottom of the file:
v.cpus = 2
To update the RAM you can use an environment variable. For example to run the
cd-pipeline application we recommend about 8Gb of RAM:
Then follow the on screen instructions.
When you first open your browser Chrome will say:
Your connection is not private
You will want to accept the self signed cert, follow these steps and return here
Team Dashboardwhich is usually called
defaultbut will be named whatever the default namespace was in your Kubernetes cluster
When you are in the
Runtime perspective of a Team or Namespace in the
fabric8 console click on the
This will list all of the installed OpenShift Templates on your installation.
To Run any of the installed templates just click the
(the green play button).
gofabric8binary which is inside the Vagrant image. e.g. to install the full Fabric8 Microservices Platform Management support then try this command instead:
gofabric8 deploy -y --domain=vagrant.f8 --app=management
To install any new
or other Kubernetes resources just drag and drop the JSON file onto
oc create -f jsonOr YamlFileOrUrl
gogsadmin/RedHat$1. Try these especially for secrets to get the pipeline to work with GOGS.
In order to communicate with the Vagrant VM from you localhost it is recommended to install the OpenShift client tools. This is explained in an extra document.
This is also useful using the fabric8 maven tooling or reusing the docker daemon inside vagrant; so that all images built are accessible inside the OpenShift environment.
Alternatively you can log into the Vagrant VM also via
ssh. The OpenShift tools (
oadmn) are installed in the VM,
Note: in case you already ran the above and want to update to the latest vagrant image, OpenShift and Fabric8 release you need to destroy and recreate the vagrant image. You can do that using:
vagrant destroy -f git pull vagrant up
Check out the troubleshooting guide for more help.