a0abe06a7cbff7818e66b66d5d27411148ad5076: update public repo contents

Author: Rodrigo Valin

README.md

@@ -2,8 +2,6 @@
 
 Welcome to the MongoDB Enterprise Kubernetes Operator. The Operator enables easy deploys of MongoDB into Kubernetes clusters, using our management, monitoring and backup platforms, Ops Manager and Cloud Manager. By installing this integration, you will be able to deploy MongoDB instances with a single simple command.
 
-Please note that this project is currently in beta, and is not yet recommended for production use.
-
 You can discuss this integration in our [Slack](https://community-slack.mongodb.com) - join the [#enterprise-kubernetes](https://mongo-db.slack.com/messages/CB323LCG5/) channel.
 
 ## Documentation ##

helm_chart/Chart.yaml

@@ -1,6 +1,6 @@
 name: mongodb-enterprise-operator
 description: MongoDB Kubernetes Enterprise Operator
-version: '0.12'
+version: '1.0'
 kubeVersion: '>=1.11'
 keywords:
 - mongodb

helm_chart/templates/operator.yaml

@@ -17,6 +17,12 @@ spec:
         app: {{ .Values.operator.name }}
     spec:
       serviceAccountName: {{ .Values.operator.name }}
+{{ if not .Values.managedSecurityContext }}
+      securityContext:
+        runAsNonRoot: true
+        runAsUser: 2000
+{{ end }}
+
       containers:
       - name: {{ .Values.operator.name }}
         image: {{ .Values.registry.repository }}/{{ .Values.operator.name }}:{{ .Values.operator.version }}
@@ -36,7 +42,7 @@ spec:
             fieldRef:
               fieldPath: metadata.namespace
 {{ end }}
-{{ if eq .Values.managedSecurityContext true}}
+{{ if eq .Values.managedSecurityContext true }}
         - name: MANAGED_SECURITY_CONTEXT
           value: 'true'
 {{ end }}

helm_chart/values.yaml

@@ -16,7 +16,7 @@ operator:
   name: mongodb-enterprise-operator
 
   # Version of mongodb-enterprise-operator and mongodb-enterprise-database images
-  version: '0.12'
+  version: '1.0'
 
 database:
   name: mongodb-enterprise-database

mongodb-enterprise.yaml

@@ -131,9 +131,15 @@ spec:
         app: mongodb-enterprise-operator
     spec:
       serviceAccountName: mongodb-enterprise-operator
+
+      securityContext:
+        runAsNonRoot: true
+        runAsUser: 2000
+
+
       containers:
       - name: mongodb-enterprise-operator
-        image: quay.io/mongodb/mongodb-enterprise-operator:0.12
+        image: quay.io/mongodb/mongodb-enterprise-operator:1.0
         imagePullPolicy: Always
 
         env:
@@ -147,7 +153,7 @@ spec:
 
 
         - name: MONGODB_ENTERPRISE_DATABASE_IMAGE
-          value: quay.io/mongodb/mongodb-enterprise-database:0.12
+          value: quay.io/mongodb/mongodb-enterprise-database:1.0
         - name: IMAGE_PULL_POLICY
           value: Always
 

samples/extended/replica-set-persistent-volumes.yaml

@@ -28,6 +28,8 @@ spec:
   persistent: true
   podSpec:
     cpu: '0.25'
+    # note: it's important to always specify memory otherwise wired tiger cache will be calculated incorrectly and
+    # monitoring tools will report the size of Kubernetes node instead of the real size of the container
     memory: 512M
     # "multiple" persistence allows to mount different directories to different Persistent Volumes
     persistence:

samples/extended/sharded-cluster-persistent-volumes.yaml

@@ -28,6 +28,8 @@ spec:
   persistent: true
   configSrvPodSpec:
     cpu: '0.5'
+    # note: it's important to always specify memory otherwise wired tiger cache will be calculated incorrectly and
+    # monitoring tools will report the size of Kubernetes node instead of the real size of the container
     memory: 512M
 
     # if "persistence" element is omitted then Operator uses the default size (5G) for mounting single Persistent Volume

samples/extended/standalone-persistent-volumes.yaml

@@ -24,6 +24,8 @@ spec:
   persistent: true
   podSpec:
     cpu: '0.25'
+    # note: it's important to always specify memory otherwise wired tiger cache will be calculated incorrectly and
+    # monitoring tools will report the size of Kubernetes node instead of the real size of the container
     memory: 512M
     # "single" persistence allows to mount different directories to single Persistent Volume
     persistence: