MongoDB Community Operator - Fails no logging

John_Menke · March 16, 2021, 3:13pm

Using the community operator - following install instructions on this page:

mongodb/mongodb-kubernetes-operator/blob/master/docs/install-upgrade.md#procedure

# Install and Upgrade the Community Kubernetes Operator #

## Table of Contents

- [Prerequisites](#prerequisites)
- [Install the Operator](#install-the-operator)
  - [Understand Deployment Scopes](#understand-deployment-scopes)
    - [Operator in Same Namespace as Resources](#operator-in-same-namespace-as-resources)
    - [Operator in Different Namespace Than Resources](#operator-in-different-namespace-than-resources)
  - [Install the Operator using Helm](#install-the-operator-using-Helm)
     - [Prerequisites to Install using Helm](#prerequisites-to-install-using-Helm)
     - [Procedure using Helm](#procedure-using-Helm)
  - [Install the Operator using kubectl](#install-the-operator-using-kubectl)
     - [Prerequisites to Install using kubectl](#prerequisites-to-install-using-kubectl)
     - [Install in a Different Namespace using kubectl](#install-in-a-different-namespace-using-kubectl)
     - [Configure the MongoDB Docker Image or Container Registry](#configure-the-mongodb-docker-image-or-container-registry)
     - [Procedure using kubectl](#procedure-using-kubectl)
- [Upgrade the Operator](#upgrade-the-operator)
- [Rotating TLS certificate for the MongoDB deployment](#rotating-tls-certificate-for-the-mongodb-deployment)

This file has been truncated. show original

I get one line of output in the pod: Running ./manager

the events show this: there does not seem to be any clue to the cause

Normal Pulled 11m (x4 over 12m) Successfully pulled image
Normal Created 11m (x4 over 12m) Created container mongodb-kubernetes-operator
Normal Started 11m (x4 over 12m) Started container mongodb-kubernetes-operator
Normal Pulling 10m (x5 over 12m) Pulling image “Quay”
Warning BackOff 2m18s (x48 over 12m) Back-off restarting failed container