Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-2570

Driver Container and Kubernetes Awareness

XMLWordPrintableJSON

    • Type: Icon: Epic Epic
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Component/s: None
    • None
      • Update the metadata handshake client.env.name field to optional.
      • Add client.env.container.
    • To Do
    • Driver Container and Kubernetes Awareness
    • 0
    • 0
    • 0
    • 100
    • Needed
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-4684 Backlog
      CXX-2715 Backlog
      CSHARP-4718 Done 2.25.0
      GODRIVER-2906 Fixed 1.13.0, 1.13.1
      JAVA-5072 Fixed 5.0.0
      NODE-5454 Fixed 5.10.0, 6.5.0
      MOTOR-1154 Duplicate
      PYTHON-3837 Fixed 4.7
      PHPLIB-1196 Blocked
      RUBY-3298 Fixed 2.20.0
      RUST-1703 Fixed 2.8.0
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion CDRIVER-4684 Backlog CXX-2715 Backlog CSHARP-4718 Done 2.25.0 GODRIVER-2906 Fixed 1.13.0, 1.13.1 JAVA-5072 Fixed 5.0.0 NODE-5454 Fixed 5.10.0, 6.5.0 MOTOR-1154 Duplicate PYTHON-3837 Fixed 4.7 PHPLIB-1196 Blocked RUBY-3298 Fixed 2.20.0 RUST-1703 Fixed 2.8.0

      Summary

      We currently lack any insight into how many customers are using Kubernetes, or even running containers. This limits us doing many things:

      • Assessing the impact of the Atlas operator on retention, usage and growth by comparing those who use containers with our Kubernetes Operator vs those who use containers but not with out Operator
      • Targetting comms and promotion to only the applicable audience for Kubernetes support of MongoDB
      • Correlating container usage in general with workload consumption

      The ask is to make as many of our drivers container aware (better yet Kubernetes-aware too) as possible and return that info in telemetry.

      We know that it's possible for at least some languages (E.g. Java) but would like this for as many of our drivers as possible.

      Motivation

      Who is the affected end user?

      • Kubernetes team
      • Sales teams wanting to correlate containerisation with workloads (containers correlated with microservices, microservices are expected to correlate with workloads

      How does this affect the end user?

      No direct impact to end users

      How likely is it that this problem or use case will occur?

      Already occuring

      If the problem does occur, what are the consequences and how severe are they?

      NA

      Is this issue urgent?

      It's blocking both Sales efforts (drive growth in microservices customers) and blocking extremely valuable product insights around our Kubernetes support

      Is this ticket required by a downstream team?

      Kubernetes team, Growth Sales team

      Is this ticket only for tests?

      Analytics, product value tracking, sales efforts

            Assignee:
            abraham.egnor@mongodb.com Abraham Egnor
            Reporter:
            dan.mckean@mongodb.com Dan Mckean
            Kevin Albertson Kevin Albertson
            Esha Bhargava Esha Bhargava
            Alex Bevilacqua Alex Bevilacqua
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: