Imixs-Cloud provides an open concept for small and medium-sized organizations to run an independent, stable and easy to manage cloud infrastructure. This project is 100% open source and based on Kubernetes - a cloud solution for automating deployment, scaling, and management of containerized applications.
You can setup an Imixs-Cloud Cluster within one day. The flexible and sustainable concept allows you to run your cloud infrastructure without any vendor lock-in. Small and medium-sized cluster environments can be hosted on virtual servers or bare metal. The project is open source and constantly under development. We sincerely invite you to participate in it! If you have any questions just open a new Issue on Github and start a Discussion.
Now, let’s get started…
The Imixs-Cloud project supports the concept of Infrastructure as Code and you will find a quick setup guide for a Kubernetes cluster below. But before you get started we should talk about the core concept of cloud architecture.
In its core a Kubernetes cluster consists of the following components:
Of course, when you set up your own cloud infrastructure with Kubernetes, you need to take care of your servers and your data. Kubernetes offers a well designed idea how to run a cluster on different nodes, providing a stable runtime environment for your containerized applications. These concepts are well documented and you will find a lot of tutorials about that. But Kubernetes does not provide you with a data infrastructure. It provides a well designed API to abstract storage from your application layer, but it leaves open the question where and how you store your data.
If you do not already have a data storage solution, you should set up a storage for your cluster environment which can be used by your applications. There are various projects which can be seamlessly integrated into Kubernetes, for example the Longhorn project provides an quick an easy setup. But within the Imixs-Cloud project, we believe a storage solution should be run independently from your Kubernetes Cluster. This has several advantages. On the one hand, the data layer is not affected in case of an outage within your Kubernetes Cluster. On the other hand, an independent storage solution can be connected from different clusters which increases the flexibility. Also if you need to change the data infrastructure, you usually do not need to make any major changes on your application side. In our view, a Ceph cluster is the best way to provide a stable and scalable storage solution for Kubernetes.
In this picture your application layer is decoupled from your data layer. You can use your data layer in various ways independent from your Kubernetes cluster which gives you more flexibility managing your data. For example if you run more than one Kubernetes cluster you can connect each to the same Ceph cluster. In general, we do not recommend building a cluster that is too big, but rather several small clusters. This allows you to migrate data and applications if your requirements grow or if you want to try something new. With the Imixs-Cloud project it is easy to setup and manage these kind of small cluster environments.
You will find a install guide in the section Ceph Quick Install.
Network is of course the most important part of a cloud environment. Similar to the Data layer there are a lot of concepts and tutorials about how to setup the network for a Kubernetes or a Ceph cluster. Most tutorials recommend that you use a second private network for the internal communication of your cluster nodes. But note: this only makes sense if your private network is notedly faster than your public network. If you do not have a separate network adapter you can run your cluster also with one public network only. You just need to take care about firewall rules. If your node to node communication is fast - 1GiBit or above - there’s absolutely nothing wrong operating within a public network. In addition, a single network also reduces complexity, which is always an advantage. With a simple firewall script you can protect your cluster easily form being accessible from outside and allowing internal communication only. See also the section Firewall.
The complete infrastructure of a Imixs-Cloud environment is described in one central configuration directory. The Configuration Directory can be synchronized with a code repository like Git. This concept is also known as Infrastructure as Code and makes it easy to role back changes if something went wrong. You can always start with a new environment by just forking this Github repository.
$ git clone https://github.com/imixs/imixs-cloud.git && rm -rf imixs-cloud/.git/
The imixs-cloud directory structure contains different sub-directories holding your applications, scripts and tools:
/- |+ management/ |- monitoring/ |- registry/ |- nginx/ |+ apps/ |+ MY-APP/ | 001-deployment.yaml ..... |+ scripts/ | apply.sh | setup.sh | delete.sh |+ tools/
apps/ is the place where where your custom business services are configured. Each sub-directory holds at least one kubernetes object description (yaml file). Optional additional configuration files are also located in this directory.
management/ in this directory you can find all the management services which are part of the Imixs-Cloud. These services are maintained by this project and can be customized for individual needs.
scripts/ provides bash scripts to setup a new kubernetes node.
tools/ provides useful tools
You can define your own services within a sub directory of the /apps/ folder. Each application has its own sub-folder and consists at least of one configuration yaml file
|+ apps/ |+ MY-APP/ | 020-deployment.yaml
kubectl apply command you can easily create or delete your services and objects defined within a apps/ or management/ sub-directory:
$ kubectl apply -f apps/MY-APP/
For example to deploy the whoami sample service you just need to call:
$ kubectl apply -f app/whoami/
In Kubernetes all resources and services are typically described in separate files. Use a naming convention to create an implicit order in which way your objects should be created.
|+ whoami/ |- 010-deployment.yaml |- 020-service.yaml |- 030-ingress.yaml
If you want to remove an already deployed service or object just use the
$ kubectl delete -f app/whoami/
The architecture of a Imixs-Cloud consists of one Kubernetes master node and one or many Kubernetes worker nodes. This basic architecture can be extended in any dimension.
For a quick setup you need at least a Debian 10 (Buster) server with a public Internet address and a user with sudo privileges. All configuration files and scripts are provided in this git repository. You can clone the repository or just copy what you need. You will also find a more detailed installation guide in the setup section.
First clone this git repository on your master node. Therefore, you may need to install git:
$ sudo apt install -y git
If you are running Fedora or CentOS than use the yum installer
$ sudo yum install -y git
next you can clone the imixs-cloud repo from github….
$ cd && git clone https://github.com/imixs/imixs-cloud.git $ cd imixs-cloud/
now you can run the setup script on your master node to install Docker and Kubernetes:
$ sudo ./scripts/setup_debian.sh
You can find details about how to create a cluster also on the official kubernets documentation.
We use a config file to make your installation as pleasant and flexible as possible. You can edit the config file
scripts/setup.yaml before if you want to change some of the default settings.
To initialize the cluster on your master node run:
$ sudo kubeadm init --config=scripts/setup.yaml
At the end the init command will give a install guide how to install the commandline tool
kubectl on your host and how to setup worker nodes.
Now you can setup the Calico Network interface. The cluster network is needed for the internal communication between your cluster nodes.
Download and deploy the calico.yaml file from here.
$ curl https://docs.projectcalico.org/manifests/calico.yaml -O $ kubectl apply -f calico.yaml
To build your cluster you can join now any worker node into your new kubernetes cluster. Just repeat the step 1 on each of your worker nodes to install the kubeadm tool. After that, you can join your worker node into your new cluster using the join command from your master node:
$ sudo kubeadm join xxx.xxx.xxx.xxx:6443 --token xxx.xxxxxxxxx --discovery-token-ca-cert-hash xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If you do not know the join command any more, run the following command on your master node:
$ kubeadm token create --print-join-command
After a new worker has joined the cluster you can check the status of your master and worker nodes:
$ kubectl get nodes
That’s it! Your kubernetes cluster is now up and running!
You will find a more detailed description about how to setup your Kubernetes cluster in the setup section. If you have any probelm or questions just open a new Issue on Github. In the following sections you will find more information about the concepts of Imixs-Cloud.
In the Imixs-Cloud project we configure some management services and tools that we find useful to manage Kubernetes and the applications running within.
The basic architecture of the Imixs-Cloud consists of the following components:
To monitor and manage your Kubernetes cluster you can use kubectl commandline tool, which is already installed on your master node. There is a huge number of commands to obtain information or change configurations. Take a look into the kubectl Cheat Sheet.
A more convenient way to obtain information about your cluster provides the tool K9s. K9s is a powerful terminal tool to interact with your Kubernetes cluster.
To install k9s in Imixs-Cloud follow the setup guide here. After you have install the tool you can start it with:
As Imixs-Cloud supports the concept of Infrastructure as Code you can setup declarative, continuous deliverys - called GitOps - with the tool Argo CD.
This allows you to controll all you application deployments form a modern Web UI and automate the synchronization of your infrastructure.
Find a detailed description how to install and setup Argo CD in the section GitOps
To access your applications from outside of your cluster Imixs-Cloud provides the NGINX Ingress Controller. This tool allows you to easily expose your services in the Intranet or to public Internet addresses. The Ingress setup of Imixs-Cloud already includes the ACME provider Let’s Encrypt. This makes it easy to publish services to the Internet in a secure way.
You can find a detailed description how to install and setup the NGINX Ingress Controller in the section ingress
Docker images are available on docker registries. The Imixs-Cloud includes a setup to run a private Docker Registry. You can find a detailed description how to install and setup the registry in the section registry
The Imixs-Cloud monitoring is based on Prometheus and Grafana which is an open-source systems monitoring and alerting toolkit. You can use this monitoring service not only to monitor your Kubernetes cluster but also to monitor specific application data. Read more about the monitoring feature here.