|
1 | 1 | # k8s_mdb |
2 | 2 |
|
3 | 3 | ## Table of Contents |
4 | | - |
5 | 4 | - [k8s_mdb](#k8s_mdb) |
6 | 5 | - [Table of Contents](#table-of-contents) |
| 6 | + - [Compatability](#compatability) |
7 | 7 | - [Description](#description) |
8 | 8 | - [Steps to Deploy](#steps-to-deploy) |
9 | 9 | - [Prerequisites](#prerequisites) |
|
19 | 19 | - [Set Up](#set-up) |
20 | 20 | - [replicaSetName](#replicasetname) |
21 | 21 | - [mongoDBVersion](#mongodbversion) |
| 22 | + - [mongoDBFCV](#mongodbfcv) |
22 | 23 | - [logLevel](#loglevel) |
23 | 24 | - [auth.scram.enabled](#authscramenabled) |
24 | 25 | - [auth.ldap.enabled](#authldapenabled) |
|
63 | 64 | - [Predeployment Checklist](#predeployment-checklist) |
64 | 65 | - [Run](#run) |
65 | 66 |
|
| 67 | +## Compatability |
| 68 | + |
| 69 | +This version of the Helm charts has been tested with MongoDB Kubernetes Operator version(s): |
| 70 | +* 1.16.0 |
| 71 | + |
66 | 72 | ## Description |
67 | 73 |
|
68 | 74 | The series of Helm Charts to deploy MongoDB Enterprise Advanced replica sets within Kubernetes with the MongoDB Kubernetes Operator and Ops Manager. |
@@ -150,9 +156,9 @@ The certificates must include the name of FQDN external to Kubernetes as a Subje |
150 | 156 |
|
151 | 157 | The secrets must be named as follows: |
152 | 158 |
|
153 | | -**\<replicaSetName\>-\<cert\>** |
| 159 | +**\mdb-<replicaSetName\>-\<cert\>** |
154 | 160 |
|
155 | | -**\<replicaSetName\>-\<clusterfile\>** |
| 161 | +**\mdb-<replicaSetName\>-\<clusterfile\>** |
156 | 162 |
|
157 | 163 | The two secrets can be created as follows: |
158 | 164 |
|
@@ -252,7 +258,8 @@ The following table describes the values required in the relevant `values.yaml`: |
252 | 258 | |Key|Purpose| |
253 | 259 | |--------------------------|------------------------------------| |
254 | 260 | |replicaSetName|Name of the cluster, used for naming the pods and replica set name| |
255 | | -|mongoDBVersion|The version of MongoDB to installed, such as `4.4.8-ent` for MognoDB Enterprise 4.4.8| |
| 261 | +|mongoDBVersion|The version of MongoDB to installed, such as `5.0.8-ent` for MongoDB Enterprise 5.0.8 Enterprise Advanced| |
| 262 | +|mongoDBFCV|A string describing the Feature Compatibility Version of the deployment, default is "5.0"| |
256 | 263 | |replicas|Number of members in the replica set (integer)| |
257 | 264 | |logLevel|Level of logging for MongoDB and agents, INFO or DEBUG| |
258 | 265 | |auth.scram.enabled|Boolean to determine if SCRAM authentication is selected. Can be selected with `auth.ldap.enabled` or by itself. At least one method must be selected| |
@@ -306,6 +313,15 @@ The version of MongoDB to deploy. The form is **\<major\>.\<release-series\>.\<p |
306 | 313 |
|
307 | 314 | As of MongoDB 5.0 the versioning has changed to **\<major\>.\<rapid\>.\<patch\>-ent**, where the rapid is a quarterly release of new features and not a develop/stable differentiator anymore. |
308 | 315 |
|
| 316 | + |
| 317 | +### mongoDBFCV |
| 318 | + |
| 319 | +The Feature Compatibility Version of the deployment. Can only ever at or one major version below the currently installed MongoDB version. |
| 320 | + |
| 321 | +Is a string value. |
| 322 | + |
| 323 | +Default is "5.0" |
| 324 | + |
309 | 325 | ### logLevel |
310 | 326 |
|
311 | 327 | Log level for the MongoDB instance and automation agent. Can be `DEBUG` or `INFO`. In the case of `DEBUG` this is equivalent to `2` for `systemLog.verbosity` in the MongoDB config file. |
|
0 commit comments