<p>I'm suddenly facing some issues in my Kubernetes application (with no event to explain it). The application has been working properly during one year but now I'm getting a CrashLoopBackOff status.</p>
<hr />
<p><strong>IMPORTANT UPDATE:</strong></p>
<p>I cannot update the Mongo replication controller in GKE, because when I commit the changes in mongo.yml (from GIT) all workloads update except mongo-controller (which is down).</p>
<p>In GKE in Workloads/Mongo-controller/Managed pods I can see that the &quot;Created on&quot; date is some days ago when the app was up. The rest of pods are updating with my commits. I don't want to delete the Mongo pod, because I suppose that we'd lost the database info/content. (The developer who created the cluster pipeline didn't schedule a backup).</p>
<hr />
<p><strong>Database</strong>: MongoDB (latest, not sure what was the one running properly)
<strong>OS</strong>: Pod running on Ubuntu 18.04
<strong>CLuster</strong>: Google Cloud Kubernetes Engines (a.k.a GKE)</p>
<p><strong>Kubectl get pods</strong></p>
<pre><code>mongo-controller-dgkkg 0/1 CrashLoopBackOff 1199 4d6h
</code></pre>
<p><strong>Logs of Mongo POD</strong></p>
<p>Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'</p>
<p>No TransportLayer configured during NetworkInterface startup&quot;}</p>
<p>Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize.</p>
<p>MongoDB starting&quot;,&quot;attr&quot;:{&quot;pid&quot;:1,&quot;port&quot;:27017,&quot;dbPath&quot;:&quot;/data/db&quot;,&quot;architecture&quot;:&quot;64-bit&quot;,&quot;host&quot;:&quot;mongo-controller-dgkkg&quot;}</p>
<p>Build Info&quot;,&quot;attr&quot;:{&quot;buildInfo&quot;:{&quot;version&quot;:&quot;4.4.1&quot;,&quot;gitVersion&quot;:&quot;ad91a93a5a31e175f5cbf8c69561e788bbc55ce1&quot;,&quot;openSSLVersion&quot;:&quot;OpenSSL 1.1.1 11 Sep 2018&quot;,&quot;modules&quot;:[],&quot;allocator&quot;:&quot;tcmalloc&quot;,&quot;environment&quot;:{&quot;distmod&quot;:&quot;ubuntu1804&quot;,&quot;distarch&quot;:&quot;x86_64&quot;,&quot;target_arch&quot;:&quot;x86_64&quot;}}}</p>
<p>Operating System&quot;,&quot;attr&quot;:{&quot;os&quot;:{&quot;name&quot;:&quot;Ubuntu&quot;,&quot;version&quot;:&quot;18.04&quot;}}</p>
<p>Options set by command line&quot;,&quot;attr&quot;:{&quot;options&quot;:{&quot;net&quot;:{&quot;bindIp&quot;:&quot;*&quot;}}}</p>
<p>Storage engine to use detected by data files&quot;,&quot;attr&quot;:{&quot;dbpath&quot;:&quot;/data/db&quot;,&quot;storageEngine&quot;:&quot;wiredTiger&quot;}</p>
<p>Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See <a href="http://dochub.mongodb.org/core/prodnotes-filesystem%22,%22tags%22:%5B%22startupWarnings%22%5D" rel="nofollow noreferrer">http://dochub.mongodb.org/core/prodnotes-filesystem&quot;,&quot;tags&quot;:[&quot;startupWarnings&quot;]</a></p>
<p>Opening WiredTiger&quot;,&quot;attr&quot;:{&quot;config&quot;:&quot;create,cache_size=1336M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress]</p>
<p><em><strong>Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade.</strong></em></p>
<p>Terminating.&quot;,&quot;attr&quot;:{&quot;reason&quot;:&quot;95: Operation not supported&quot;}}</p>
<p>Fatal assertion&quot;,&quot;attr&quot;:{&quot;msgid&quot;:28595,&quot;file&quot;:&quot;src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp&quot;,&quot;line&quot;:1101}}</p>
<p>\n\n***aborting after fassert() failure\n\n</p>
<p><strong>My Mongo.yml:</strong></p>
<pre><code>apiVersion: v1
kind: Service
metadata:
  name: mongo
  namespace: $KUBE_NAMESPACE-$CI_ENVIRONMENT_SLUG
  labels:
    name: mongo
spec:
  ports:
    - port: 27017
      targetPort: 27017
  selector:
    name: mongo
---
apiVersion: v1
kind: ReplicationController
metadata:
  name: mongo-controller
  namespace: $KUBE_NAMESPACE-$CI_ENVIRONMENT_SLUG
  labels:
    name: mongo
spec:
  replicas: 1
  template:
    metadata:
      labels:
        name: mongo
    spec:
      containers:
      - image: mongo
        name: mongo
        ports:
        - name: mongo
          containerPort: 27017
          hostPort: 27017
        volumeMounts:
            - name: mongo-persistent-storage
              mountPath: /data/db
      volumes:
        - name: mongo-persistent-storage
          gcePersistentDisk:
            pdName: mongo-disk-$CI_ENVIRONMENT_SLUG
            fsType: ext4
</code></pre>
<p>PD: Maybe I should update my ReplicationController to Deployment (recommended), but being a database container we always configure it in that way. However I tried that, and nothing changed.</p>

AlexAcc
<p>I solved this issue editing the Replication Controller online from the Google Cloud Console.</p>
<p>Access to: &quot;Kubernetes Engine&quot; &gt; &quot;Workload&quot; &gt; &quot;mongo-controller&quot; &gt; &quot;Managed pods&quot; &gt; &quot;mongo-controller-XXXXX&quot;</p>
<p>...and press EDIT button (in the top navbar). You can edit the configuration online in real time. I simply specified the Mongo version (4.2.10) in the image, and  everything woked as expected.</p>
<pre><code>    spec:
      replicas: 1
      selector:
        name: mongo
      template:
        metadata:
          creationTimestamp: null
          labels:
            name: mongo
        spec:
          containers:
          - image: mongo: 4.2.10

          (...)
</code></pre>
