Joel

My feedback

  1. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Tools » Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Joel supported this idea  · 
  2. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Tools » Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Joel supported this idea  · 
  3. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Ops Tools » Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Joel commented  · 

    Permissions should include allowing mongodump --oplog the entire ReplicaSet (e.g. admin DB) and execute db.fsyncLock() in order to perform filesystem level backups.

    Joel supported this idea  · 
  4. 59 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Atlas » Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    Joel supported this idea  · 
  5. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Ops Tools » Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    Joel supported this idea  · 
  6. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Ops Tools » Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Joel commented  · 

    Hi Andrey,

    The HELM chart you are referring to is about the deployment of the Operator.

    This suggestion is about a HELM chart for the resources needed to deploy a MongoDB instance. Meaning MongoDB CR, MongoDBUser CR(s) and secret(s) for the User.

    Joel shared this idea  · 
  7. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Tools » Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    Joel shared this idea  · 
  8. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Ops Tools » Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Joel supported this idea  · 
  9. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Ops Tools » Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Joel commented  · 

    Totally agree. I would describe it as follows:

    The OpsManager cannot be fully configured via the MongoDBOpsManager resource. There is interaction with the OpsManager API needed for:
    - Initial settings wizard (mailserver, email addresses etc.)
    - Backup integration
    - Creation of a Organization, API keys and IP whitelisting in order to be able to create MongoDB instances for the S3 metadata storage and oplog store
    - After that Create a Secret and ConfigMap with the data returned from OpsManager

    Provide a k8s native way to Configure the OpsManager without any interaction towards the OpsManager API

    Option 1: Provide a way to add this configuration directly in the MongoDBOpsManager resource

    Option 2: Provide a way to Configure the OpsManager settings via ConfigMap

    An error occurred while saving the comment
    Joel commented  · 

    When deploying a MongoDB resource to a newly installed Operator and OpsManager the user has to

    Create an Organization, API keys and IP whitelisting in OpsManager
    Create a Secret and ConfigMap with the data returned from OpsManager
    Specify this Configmap as "configMapRef" in the MongoDB resource.

    Please provide a k8s native way to deploy a MongoDB instance without any interaction towards the OpsManager API. The MongoDB Operator should create the Organization, API keys and IP whitelisting in OpsManager and create the secret and configmap.

    Option 1: Create a CRD "MongoDBOpsManagerOrganization" that has a reference to a secret (containing the private key) and an IP whitelist as parameter. The MongoDB resource then references this MongoDBOpsManagerOrganization

    Option 2: The MongoDB Operator automatically creates an Organization per Namespace containing MongoDB resources. The user does not need to create any Organization, API keys, IP whitelisting, Secret and ConfigMaps.

    Joel supported this idea  · 
  10. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Ops Tools » Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    Joel shared this idea  · 
  11. 9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Tools » Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Andrey responded

    We are going to address this later in July-August.
    When Backup configuration is straight forward, workflow around deleting or modifying it is a bit more complicated. We Would like to get it right.

    Joel supported this idea  · 
  12. 34 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Ops Tools » Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Andrey responded

    We are going to start POC in July to figure this out. Our goal is to form a single cluster that can fallback between different K8S clusters.

    Joel supported this idea  · 

Feedback and Knowledge Base