Page History
...
- JS7 can be set up for use with a Kubernetes Cluster using the Linux based JS7 container images for Docker® containers which ship with a current Alpine base image and OpenJDK.
- Docker® Container images for JS7 are publicly available from https://hub.docker.com/r/sosberlin/js7.
- Instructions on how to run containers for JS7 components products can be found from the JS7 - Installation for Docker Containers article series.
- Users deploy JS7 components products by creating a Kubernetes deployment object from a YAML deployment file, for details see JS7 - How to deploy to a Kubernetes Cluster
...
Update the package database
Code Block sudo yum check-update
Install the dependencies
Code Block sudo yum install -y yum-utils device-mapper-persistent-data lvm2
Add and enable the Docker Repository for CentOS
Code Block sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
Install the latest Docker version for CentOS
Code Block sudo yum install docker-ce
After successful installation the output will include the string
Complete!
You may be prompted to accept the GPG key. This is to verify that the fingerprint matches. A fingerprint can look like this, if you consider the fingerprint being correct, accept it:Code Block 060A 61C5 1B55 8A7F 742B 77AA C52F EB6B 621E 9F35
Manage Docker service
With Docker being installed the systemd service has to be started. Start and enable Docker from systemd using the following commands:Code Block sudo systemctl start docker.service sudo systemctl enable docker.service
To check that Docker is up and running use the command:
Code Block sudo systemctl status docker.service
Set up the Kubernetes Repository
...
When initializing
kubeadm
directly thenkubeadm
might raise the error:Code Block Some fatal errors occurred: [ERROR CRI]: container runtime is not running Status from runtime service failed” err=”rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService”
To resolve the above problem users should delete the
config.tomal
file and restart containerd using the following commands:Code Block sudo rm /etc/containerd/config.toml systemctl restart containerd
Initialize
kubeadm
, create required directories and manage Kubernetes Cluster configuration:Code Block sudo kubeadm init mkdir $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config export KUBECONFIG=/etc/kubernetes/admin.conf
Enable and restart Docker and Kubernetes services from systemd.
Code Block sudo systemctl enable docker.service sudo service kubelet restart sudo chown -R centos:centos kubernetes/
To initialize the CNI plugin update your CNI plugins and edit the CNI config files. Use the following command to create the file and open it for editing:
Code Block sudo vi /etc/cni/net.d/10-containerd-net.conflist
Once the file is open, press the I key to enter insert mode and paste the following contents:
Code Block { "cniVersion": "1.0.0", "name": "containerd-net", "plugins": [ { "type": "bridge", "bridge": "cni0", "isGateway": true, "ipMasq": true, "promiscMode": true, "ipam": { "type": "host-local", "ranges": [ [{ "subnet": "10.88.0.0/16" }], [{ "subnet": "2001:db8:4860::/64" }] ], "routes": [ { "dst": "0.0.0.0/0" }, { "dst": "::/0" } ] } }, { "type": "portmap", "capabilities": {"portMappings": true}, "externalSetMarkChain": "KUBE-MARK-MASQ" } ] }
Once pasted, press escape to exit insert mode. Then enter
:x
to save the file and exit.We have to taint this node. We can do this by using the
kubectl taint
commandCode Block kubectl taint nodes <name-node-master> node-role.kubernetes.io/control-plane:NoSchedule-
Set up Pod network for the Kubernetes Cluster.
Code Block kubectl get nodes
With the above steps, the setup of the Kubernetes Cluster is completed. In the next step, users can create the Kubernetes YAML deployment files to deploy JS7 components products to the Kubernetes Cluster.
...