MongoDB Enterprise Kubernetes Operator
OTHER License
Bot releases are hidden (Show)
Published by antonlisovenko over 5 years ago
Published by antonlisovenko over 5 years ago
project
config map and credentials
secret and performs rolling upgrade for relevant Kubernetes resourcesPublished by antonlisovenko almost 6 years ago
controller-runtime
library. This fixed some problems when Operator could leave resources in inconsistent state and introduced proper reconciliation process.
finalizer
headers it's important to delete mongodb resources before deleting Operator/namespace otherwise the deletion operation can get stuck. More details in the docs
status
field for all MongoDB Kubernetes resourceslogLevel
(INFO
by default) was added. Automation Agent and mongodb logs are merged in to a single log stream.Published by antonlisovenko almost 6 years ago
Published by antonlisovenko about 6 years ago
Published by rodrigovalin about 6 years ago
CustomResourceDefinition
objects any more, they need to be created manually by the administrator. A new yaml file is provided (crds.yaml
) that can be applied to create/configure these objects.ClusterRoles
are not required any more. We have changed the way the Operator watches resources. Until the last release, the Operator would watch for any resource on any Namespace. With 0.3, the operator will watch for resources in the same Namespace that it was created in. To support multiple namespaces, multiple Operators can be installed. This allows isolation of MongoDB deployments.PersistentVolumes
are mounted.SecurityContexts
for Pods. This solves an issue with OpenShift which disallows this setting when SecurityContextContraints
are in place. If using Helm, the variable managedSecurityContext
set to true
will tell the operator to not create SecurityContext
s for Pods, satisfying the OpenShift requirement.projectName
and orgId
is now used to configure Ops Manager or Cloud Manager. If a project with this projectName
does not exist, it will be created by the Operator.Published by rodrigovalin about 6 years ago
The WiredTiger Cache Size for individual mongod
s is now set by the operator, considering the memory limits of the mongod
container. The formula used to calculate this attribute can be found in this this document.