- Check if installed version of the component is lower than required. Version upgrade abiltiy.
- Cleanup. Remove all installable components along with config files.
- Abiltiy to choose between KVM and VB in linux environment.
Install VirtualBox or KVM on Linux by yourself.
Assume your projects path is ~/PROJECTS
cd ~/PROJECTS && git clone https://github.com/Antiarchitect/testapp-postgresql.git
cd ~/PROJECTS/testapp-postgresql/
git submodule init
git submodule update --remote
~/PROJECTS/kubeboot/kb.sh ~/PROJECTS/testapp-postgresql/
It should open up automatically, but you can easily access it by typing:
minikube dashboard
Application should open automatically if web_service_name
parameter is set in kubeboot.yaml
, but you can easily
find out what url your apllication have (if any):
export NODE_PORT=$(kubectl get --namespace default -o jsonpath="{.spec.ports[0].nodePort}" services my-rails-dev-helm-rails)
export NODE_IP=$(kubectl get nodes --namespace default -o jsonpath="{.items[0].status.addresses[0].address}")
echo http://$NODE_IP:$NODE_PORT
kubeboot.yaml
is a simple config file stored on the app side to tell kubeboot some specifics about your app you want
to run inside the local kubernetes cluster.
Parameter | Description |
---|---|
helm_path |
Path to the helm chart. |
values_filename |
File name with dev values. |
app_image_tag |
Docker image with your application runtime. Will be used to name Helm release. |
web_service_name |
Kubernetes service holding http server so kubeboot can open app in the browser. |
dockerfiles |
Array of hashes with all docker images to be built from your .dockerfiles . |
sync_precreate_paths |
Paths that should be precreated before sync with correct permissions |
Is the place all your service-related dockerfiles for development are located in.
Is your application Helm chart.