MongoDB Kubernetes Operator 0.8.3
MongoDBCommunity Resource
- Changes
- Introduced support for X.509 authentication for client and agent
spec.security.authentication.modes
now supports valueX509
- The agent authentication mode will default to the value in
spec.security.authentication.modes
if there is only one specified. - Otherwise, agent authentication will need to be specified through
spec.security.authentication.agentMode
. - When agent authentication is set to
X509
, the fieldspec.security.authentication.agentCertificateSecretRef
can be set (default isagent-certs
). - The secret that
agentCertificateSecretRef
points to should contain a signed X.509 certificate (under thetls.crt
key) and a private key (undertls.key
) for the agent. - X.509 users can be added the same way as before under
spec.users
. Thedb
field must be set to$external
for X.509 authentication. - For these users,
scramCredentialsSecretName
andpasswordSecretRef
should not be set. - Sample resource yaml
- Sample agent certificate yaml
- Add support for configuring logRotate on the automation-agent. The settings can be found under
processes[n].logRotate.<setting>
. - Additionally, systemLog can now be configured. In particular the settings:
path
,destination
andlogAppend
. - MongoDB 7.0.0 and onwards is not supported. Supporting it requires a newer Automation Agent version. Until a new version is available, the Operator will fail all deployments with this version. To ignore this error and force the Operator to reconcile these resources, use
IGNORE_MDB_7_ERROR
environment variable and set it totrue
. - Introduced support for ARM64 architecture
- A manifest supporting both AMD64 and ARCH64 architectures is released for each version.
ubuntu
based images are deprecated, users should move toubi
images next release.
- Introduced support for X.509 authentication for client and agent
Updated Image Tags
- mongodb-kubernetes-operator:0.8.3
All the images can be found in:
https://quay.io/mongodb
https://hub.docker.com/r/mongodb/mongodb-community-server