mongo-k8s-sidecar | Kubernetes sidecar for Mongo | OAuth library

A persistent volume is just the declaration of availability of some storage inside your kubernetes cluster. There is no binding with your pod at this stage.

Since your pod is deployed through a StatefulSet, there should be in your cluster one or more PersistentVolumeClaims which are the objects that connect a pod with a PersistentVolume.

In order to manually bind a PV with a PVC you need to edit your PVC by adding the following in its spec section:

I never used this sidecar - I manually setup replica, but I guess you are missing KUBERNETES_MONGO_SERVICE_NAME to use stable network IDs as mentioned in sidecar repository

From Kubernetes source:

Limits and requests for memory are measured in bytes. You can express memory as a plain integer or as a fixed-point integer using one of these suffixes: E, P, T, G, M, K. You can also use the power-of-two equivalents: Ei, Pi, Ti, Gi, Mi, Ki. For example, the following represent roughly the same value:

128974848, 129e6, 129M, 123Mi

So those are the "bibyte" counterparts, like user2864740 commented.

A little info on those orders of magnitude:

The kibibyte was designed to replace the kilobyte in those computer science contexts in which the term kilobyte is used to mean 1024 bytes. The interpretation of kilobyte to denote 1024 bytes, conflicting with the SI definition of the prefix kilo (1000), used to be common.

So, as you can see, 5G means 5 Gigabytes while 5Gi means 5 Gibibytes. They amount to:

• 5 G = 5000000 KB / 5000 MB
• 5 Gi = 5368709.12 KB / 5368.70 MB

Therefore, in terms of size, they are not the same.

Add bind_ip to command:

It seems like the error you are getting is from the mongo-sidecar container in the pod. As for why the mongo container is failing, can you obtain more detailed information? It could be something like a failed PVC.

--smallfiles is not supported in newest mongo (4.2) you can check it in doc, you are not specifying image tag so newest latest is pull in this case mongo 4.2.

If you set image: mongo:4.0 your configuration should be correct.

The connection to your Mongodb database doesn't work for two reasons:

1. You cannot connect to high-available MongoDB deployment running inside your Kubernetes cluster using Pods DNS names. These unique POD names: mongo-0.mongo, mongo-1.mongo, with corresponding FQDNs as mongo-0.mongo.default.svc.cluster.local, mongo-1.mongo.default.svc.cluster.local, can be only reached within the K8S cluster. You have an Express web application that runs on client side (Web browser), and needs to connect to your mongodb from outside of cluster.

2. Connection string: you should connect to primary node via Kubernetes service name, that abstracts access to the Pods behind the replica sets.

Solution:

Create a separate Kubernetes Service of LoadBalancer or NodePort type for your Primary ReplicaSet, and use :27017 in your connection string.

I would encourage you to take a look at official mongodb helm chart, to see what kind of manifest files are required to satisfy your case.

Hint: use '--set service.type=LoadBalancer' with this helm chart

StatefulSet support has been recently added, but it's not in a release yet.

https://github.com/istio/pilot/pull/896

According to original solution: https://github.com/cvallance/mongo-k8s-sidecar/issues/75

You have to create role binding which will grant the default service account view permissions: