Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Using OpenEBS on Azure Kubernetes Cluster #1335
I created a three node Kubernetes cluster in AZURE of Standard_A0 type. At this point this is the sc output
I used the openebs operator and storageclass yaml and then the postgress cluster yaml files to created the storage class and Statefulset upon which I see that one of the pod is not completely up. I believe the error points to the volume, I would appreciate any pointers.
kubectl get pods
Below are excerpts from kubectl describe pod pgset-0
Warning FailedScheduling 25m (x3 over 25m) default-scheduler PersistentVolumeClaim is not bound: "pgdata-pgset-0" (repeated 3 times)
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
az aks create --resource-group JayPgResourceGroup --name JayPgDbReplicaSet --node-count 3 --kubernetes-version 1.8.7 --node-vm-size Standard_A0 --generate-ssh-keys
Create the openebs storage classes
Create the crunchy data postgres as explained in https://docs.openebs.io/docs/CrunchyPostgres.html
Anything else we need to know?:
@jay-wilson , thanks for trying OpenEBS on AKS & sharing the logs ! Here is some initial analysis on this cluster:
The AKS cluster runs ubuntu 16.04 LTS with the kubelet running in a container (debian-jessie 8). The kubelet logs show the absence of the iSCSI initiator, due to which the volume is not attached to the node.
Configuring the kubelet to run w/ iSCSI utils should ideally fix this
Need to find a way to automate (#1149) installing the iscsi initiator on the kubelet container. The following steps were followed to manually install:
@kmova @yudaykiran Just thinking aloud here.
2/ Can we check if pod probes can do the apt-get install stuff
All these to avoid plumbing code around ssh & thinking from docker perspective.
@AmitKumarDas kubelet is not deployed as a pod, rather, the kubelet service is run inside a hyperkube container. i don't think this can be fixed from the Kubernetes end. It is more of a cloud-init that brings the VM up and has some configuration for running the kubelet service inside this container. This is similar to how coreos runs all its services inside containers.
referenced this issue
Mar 21, 2018
Solution guide to setup OpenEBS in Azure : https://github.com/openebs/openebs-docs/blob/master/docs/openebs_azure.md
referenced this issue
Apr 5, 2018
(just passing by)
To elaborate on @yudaykiran's comment. hyperkube and virtual kubelet are two different things.