{"id":2428,"date":"2019-08-08T17:52:43","date_gmt":"2019-08-08T17:52:43","guid":{"rendered":"https:\/\/owncloud.com\/?p=2428"},"modified":"2020-07-08T10:46:53","modified_gmt":"2020-07-08T10:46:53","slug":"running-owncloud-in-kubernetes-with-rook-ceph-storage-step-by-step","status":"publish","type":"post","link":"https:\/\/owncloud.com\/de\/blogs\/running-owncloud-in-kubernetes-with-rook-ceph-storage-step-by-step\/","title":{"rendered":"Running ownCloud in Kubernetes With Rook Ceph Storage \u2013 Step by Step"},"content":{"rendered":"
\n
The first part<\/a> of this series explained what we need for an ownCloud deployment in a Kubernetes cluster and gave a high level overview. You can find the example files for this guide in this GitHub repository<\/a>.<\/div>\n<\/div>\n
\n

Preparations<\/h2>\n

To follow this guide, you need admin access to a Kubernetes cluster with an Ingress controller. If you don\u2019t have that already, you can follow these steps:<\/p>\n

Kubernetes Cluster Access<\/h3>\n

If you don\u2019t have a Kubernetes cluster, you can try using the following projects\u00a0xetys\/hetzner-kube on GitHub<\/a>,\u00a0Kubespray<\/a>\u00a0and\u00a0others (Kubernetes documentation)<\/a>.<\/p>\n

minikube is not enough when started with the default resources, be sure to give minikube extra resources otherwise you will run into problems! Be sure to\u00a0add the following flags\u00a0to the\u00a0minikube start<\/code>\u00a0command:\u00a0--memory=4096 --cpus=3 --disk-size=40g<\/code>.<\/p>\n

You should have\u00a0cluster-admin<\/code>\u00a0access to the Kubernetes cluster! Other access can also work, but due to the nature of objects that are created along the way it is easier to have the\u00a0cluster-admin<\/code>\u00a0access.<\/p>\n

Kubernetes Cluster<\/h3>\n

Ingress Controller<\/h4>\n

WARNING:\u00a0Only follow this section, if your Kubernetes cluster does not have an Ingress controller yet.<\/p>\n

We are going to install the Kubernetes NGINX Ingress Controller.<\/p>\n

# Taken from<\/span> https:\/\/github.com\/kubernetes\/ingress-nginx\/blob\/master\/deploy\/static\/mandatory.yaml<\/span>\r\nkubectl apply -f ingress-nginx\/\r\n<\/code><\/pre>\n
The instructions shown here are for an environment without\u00a0LoadBalancer<\/code>\u00a0Service type support (e.g., bare metal, \u201cnormal\u201d VM provider, not cloud), for installation instructions for other environments check out\u00a0Installation Guide \u2013 NGINX Ingress Controller<\/a>.<\/p>\n
# Taken from<\/span> https:\/\/github.com\/kubernetes\/ingress-nginx\/blob\/master\/deploy\/static\/provider\/baremetal\/service-nodeport.yaml<\/span>\r\nkubectl apply -f ingress-nginx\/service-nodeport.yaml\r\n<\/code><\/pre>\n
As these are bare metal installation instructions, the NGINX Ingress controller will be available through a Service of type\u00a0NodePort<\/code>. This Service type exposes one or more ports on all Nodes in the Kubernetes cluster.<\/p>\n
To get that port run:<\/p>\n
$ kubectl get -n ingress-nginx service ingress-nginx\r\nNAME<\/span>            TYPE<\/span>       CLUSTER-IP       EXTERNAL<\/span>-IP   PORT(S)                      AGE\r\ningress-nginx   NodePort   10.108.<\/span>254.160<\/span>   <none<\/span>>        80<\/span>:30512<\/span>\/TCP,443<\/span>:30243<\/span>\/TCP   3m\r\n<\/code><\/pre>\n
In that output you can see the NodePorts for HTTP and HTTPS on which you can connect to the NGINX Ingress controller and ownCloud later.<\/p>\n
Namespaces<\/h4>\n
Through the whole installation we will create 4 Namespaces:<\/p>\n
Though as written you probably want to look into a more \u201csolid\u201d way to expose the NGINX Ingress controller(s), for bare metal where there is no Kubernetes LoadBalancer integration one can consider using\u00a0hostNetwork<\/code>\u00a0option for that:\u00a0bare-metal considerations \u2013 NGINX Ingress Controller<\/a>.<\/p>\n