7bd7296cff21926c8174a4f2483fd1ccc5e6ca5e: update public repo contents

Author: chatton

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: Bug report
+about: File a report about a problem with the Operator
+title: ''
+labels: ''
+assignees: ''
+
+---
+**What did you do to encounter the bug?**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**What did you expect?**
+A clear and concise description of what you expected to happen.
+
+**What happened instead?**
+A clear and concise description of what happened instead
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Operator Information**
+ - Operator Version
+ - Base Images used (ubuntu or UBI)
+
+**Ops Manager Information**
+ - Ops Manager Version
+ - Is Ops Manager managed by the Operator or not?
+ - Is Ops Manager in Local Mode?
+
+**Kubernetes Cluster Information**
+ - Distribution:
+ - Version:
+ - Image Registry location (quay, or an internal registry)
+
+**Additional context**
+Add any other context about the problem here.
+
+If possible, please include:
+ - `kubectl describe` output
+ - yaml definitions for your objects
+ - log files for the operator, database pods and Ops Manager
+ - An [Ops Manager Diagnostic Archive](https://docs.opsmanager.mongodb.com/current/tutorial/retrieve-debug-diagnostics)

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+    - name: MongoDB Support
+      url: https://support.mongodb.com
+      about: Please use the Support Center to receive official support within a timeline. Use this for urgent requests.
+    - name: MongoDB Feedback
+      url: https://feedback.mongodb.com/forums/924355-ops-tools
+      about: Use our Feedback page for making feature requests.

README.md

@@ -2,15 +2,19 @@
 
 Welcome to the MongoDB Enterprise Kubernetes Operator. The Operator enables easy deploy of the following applications into Kubernetes clusters:
 * MongoDB - Replica Sets, Sharded Clusters and Standalones, with authentication, TLS and many more options.
-* Ops Manager - our enterprise management, monitoring and backup platform for MongoDB. The Operator can install and manage Ops Manager in Kubernetes for you.
+* Ops Manager - our enterprise management, monitoring and backup platform for MongoDB. The Operator can install and manage Ops Manager in Kubernetes for you. Ops Manager can manage MongoDB instances both inside and outside Kubernetes.
 
-The Operator requires access to one of our database management tools - Ops Manager or Cloud Manager - to deploy MongoDB instances. 
+The Operator requires access to one of our database management tools - Ops Manager or Cloud Manager - to deploy MongoDB instances.
 You may run Ops Manager either inside or outside Kubernetes, or may use Cloud Manager (cloud.mongodb.com) instead.
 
 The Operator is currently Generally Available, supported by the [MongoDB Support Team](https://support.mongodb.com/). If you need urgent help, please file a support ticket.
 For non-urgent requests, you may file a Github Issue here in the repo.
 
-You can discuss this integration in our new [Community Forum](https://community.mongodb.com/) - please use the tag [enterprise-kubernetes-operator](https://community.mongodb.com/tags/enterprise-kubernetes-operator).
+You can discuss this integration in our new [Community Forum](https://developer.mongodb.com/community/forums/) - please use the tag [kubernetes-operator](https://developer.mongodb.com/community/forums/tag/kubernetes-operator)
+
+Here are some talks from MongoDB Live 2020 about the Operator:
+* [Kubernetes, MongoDB, and Your MongoDB Data Platform](https://www.youtube.com/watch?v=o1fUPIOdKeU)
+* [Run it in Kubernetes! Community and Enterprise MongoDB in Containers](https://www.youtube.com/watch?v=2Xszdg-4T6A)
 
 ## Documentation ##
 
@@ -30,11 +34,11 @@ You can discuss this integration in our new [Community Forum](https://community.
 
 ## Requirements ##
 
-Please refer to the [Installation Instructions](https://docs.mongodb.com/kubernetes-operator/stable/tutorial/plan-k8s-operator-install/) 
-to see which Kubernetes and Openshift versions the Operator is compatible with 
+Please refer to the [Installation Instructions](https://docs.mongodb.com/kubernetes-operator/stable/tutorial/plan-k8s-operator-install/)
+to see which Kubernetes and Openshift versions the Operator is compatible with
 
-To work with MongoDB resource this Operator requires [Ops Manager](https://docs.opsmanager.mongodb.com/current/) (Ops Manager can 
-be installed into the same Kubernetes cluster by the Operator or installed outside of the cluster manually) 
+To work with MongoDB resource this Operator requires [Ops Manager](https://docs.opsmanager.mongodb.com/current/) (Ops Manager can
+be installed into the same Kubernetes cluster by the Operator or installed outside of the cluster manually)
 or [Cloud Manager](https://cloud.mongodb.com/user#/cloud/login).
 > If this is your first time trying the Operator, Cloud Manager is easier to get started
 
@@ -75,11 +79,9 @@ or clone this repo, make any edits you need, and apply it from your machine.
 
 ### Installation using Helm Chart
 
-If you have installed the Helm client locally then you can run (note that `helm install` is a less preferred way as makes upgrades more complicated.
-`kubectl apply` is a much clearer way of installing/upgrading):
+If you have installed the Helm client locally then you can run:
 
-    helm template helm_chart > operator.yaml
-    kubectl apply -f operator.yaml
+    helm install mongodb-enterprise-operator helm_chart --values helm_chart/values.yaml
 
 You can customize installation by simple overriding of helm variables, for example use `--set operator.env="dev"` to run the Operator in development mode
 (this will turn logging level to `Debug` and will make logging output as non-json)
@@ -190,11 +192,11 @@ Note, that it takes up to 8 minutes to initialize the Application Database and s
 
 Now you can use the Ops Manager application to create MongoDB objects. You need to follow the
 [instructions](https://docs.mongodb.com/kubernetes-operator/stable/tutorial/create-operator-credentials/#prerequisites)
-to prepare keys and enable network access to Ops Manager. 
+to prepare keys and enable network access to Ops Manager.
 Then you need to perform the standard steps necessary to create MongoDB resource:
-* Create a [credentials Secret](https://docs.mongodb.com/kubernetes-operator/stable/tutorial/create-operator-credentials/#create-k8s-credentials) 
-* Create a [connection ConfigMap](https://docs.mongodb.com/kubernetes-operator/stable/tutorial/create-project-using-configmap/) 
-  * Note, that you should use the value from `status.opsManager.url` in MongoDBOpsManager Resource as a value for `baseUrl` field in the ConfigMap  
+* Create a [credentials Secret](https://docs.mongodb.com/kubernetes-operator/stable/tutorial/create-operator-credentials/#create-k8s-credentials)
+* Create a [connection ConfigMap](https://docs.mongodb.com/kubernetes-operator/stable/tutorial/create-project-using-configmap/)
+  * Note, that you should use the value from `status.opsManager.url` in MongoDBOpsManager Resource as a value for `baseUrl` field in the ConfigMap
 
 ## Accessing Ops Manager UI (from a browser)
 

crds.yaml

@@ -99,6 +99,12 @@ spec:
                 startupOptions:
                   type: object
 
+            backup:
+              type: object
+              properties:
+                mode:
+                  type: string
+                  enum: ["enabled", "disabled", "terminated"]
             # Generic PodSpec configuration
             podSpec:
               type: object

helm_chart/crds/mongodb.mongodb.com.yaml

@@ -99,6 +99,12 @@ spec:
                 startupOptions:
                   type: object
 
+            backup:
+              type: object
+              properties:
+                mode:
+                  type: string
+                  enum: ["enabled", "disabled", "terminated"]
             # Generic PodSpec configuration
             podSpec:
               type: object

helm_chart/templates/operator-roles.yaml

@@ -47,6 +47,14 @@ rules:
   - watch
   - delete
   - update
+- apiGroups:
+  - ""
+  resources:
+  - pods
+  verbs:
+  - get
+  - list
+  - watch
   {{- if eq (.Values.operator.watchNamespace | default "") "*" }}
 - apiGroups:
   - ""

helm_chart/templates/operator.yaml

@@ -117,5 +117,5 @@ spec:
       port: 40000
       protocol: TCP
   selector:
-    app: {{ .Values.operator.name }}
+    app.kubernetes.io/name: {{ .Values.operator.name }}
 {{- end }}

mongodb-enterprise-openshift.yaml

@@ -83,6 +83,14 @@ rules:
   - watch
   - delete
   - update
+- apiGroups:
+  - ""
+  resources:
+  - pods
+  verbs:
+  - get
+  - list
+  - watch
 - apiGroups:
   - mongodb.com
   resources:

mongodb-enterprise.yaml

@@ -83,6 +83,14 @@ rules:
   - watch
   - delete
   - update
+- apiGroups:
+  - ""
+  resources:
+  - pods
+  verbs:
+  - get
+  - list
+  - watch
 - apiGroups:
   - mongodb.com
   resources:

openshift-install.md

@@ -8,8 +8,8 @@ for your OpenShift installation to be able to fetch images from this registry.
 ## Create your OpenShift Secret
 
 First, complete the instructions
-[here](https://access.redhat.com/terms-based-registry/#/token/openshift3-test-cluster/docker-config). Unfortunately,
-these instructions refer to a `registry.redhat.io` Registry which is not the one we need, but they accept the same
+[here](https://access.redhat.com/terms-based-registry/#/accounts). Unfortunately,
+these instructions refer to a `registry.redhat.io` registry which is not the one we need, but they accept the same
 credentials. First, click on "view its contents" to display the contents we need, and save these contents into a json
 file. This file includes 1 entry for `registry.redhat.io`; replicate that entry with a new name,
 "`registry.connect.redhat.com`", as in the following example: