The minikube-based development setup enables users to bring up a local implementation of the OIH Framework based on the current service images found on Docker Hub, while individually selecting which services they would like to deploy from their own local source folders.
Please make sure to clone the monorepo before you start.
The development environment requires:
Make sure that minikube is endowed with sufficient resources. We suggest at least:
- 8GB of memory
- 4 CPUs
The setup script will attempt to provision the minikube instance with these values by default on execution. This can be changed by altering the variables MK_MEMORY and MK_CPUS.
Before running the setup script, the location of your NFS server must be updated in ./1-Platform/2.1-sourceCodeVolume.yaml. The server host is the IP address which minikube uses to access the host. In order to verify your server address, you will need to start minikube and then execute the following command:
minikube ssh grep host.minikube.internal /etc/hosts | cut -f1
The path is the path to the root of your cloned repository / base path of the framework
nfs: server: 192.168.64.1 path: '/Users/user/projects/openintegrationhub'
From the $OIH_ROOT/dev-tools/minikube folder, call the setup script
The script will check for prerequisites, and attempt to build all services. The script automates the steps found in the minikube Local Installation Guide on the parent page.
Additionally, the following options may be sent in the arguments to
-c: Clear Minikube. The minikube cluster will be deleted and rebuilt from scratch.
-s: Skip Deployment. Any service names which are provided as arguments to this flag will not be included in the running cluster. They will be temporarily deployed to ensure all dependencies are met, then deleted at the end of startup.
bash ./setup.sh -s meta-data-repository, snapshots-service
-d: Development Mode. Any service names which are provided as arguments to this flag will be deployed from the local source files. Instead of being deployed from the Docker Hub containers, a generic node container will be deployed, and the source directory will be mounted through NFS. Changes to the source files will be watched and reflected in the running containers.
bash ./setup.sh -d iam, component-orchestrator
-i: Use Custom Component Image. This setup automatically deploys a development connector and includes it in sample flows. To change the container which is used for this connector, include an image name here. (Default image:
-p: Start Proxy. If this flag is set, then
kubectlwill set up proxy connections to Mongo, RabbitMQ, and Redis for use in debugging backend and messaging systems.