[DRIVERS-2570] Driver Container and Kubernetes Awareness Created: 07/Mar/23  Updated: 06/Dec/23

Status: Implementing
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Epic Priority: Unknown
Reporter: Dan Mckean Assignee: Abraham Egnor
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to MOTOR-1154 Driver Container and Kubernetes Aware... Closed
split to CDRIVER-4684 Driver Container and Kubernetes Aware... Backlog
split to CSHARP-4718 Driver Container and Kubernetes Aware... Backlog
split to CXX-2715 Driver Container and Kubernetes Aware... Backlog
split to NODE-5454 Driver Container and Kubernetes Aware... Backlog
split to PHPLIB-1196 Driver Container and Kubernetes Aware... Blocked
split to GODRIVER-2906 Driver Container and Kubernetes Aware... Closed
split to JAVA-5072 Driver Container and Kubernetes Aware... Closed
split to PYTHON-3837 Driver Container and Kubernetes Aware... Closed
split to RUBY-3298 Driver Container and Kubernetes Aware... Closed
split to RUST-1703 Driver Container and Kubernetes Aware... Closed
Driver Changes: Needed
Quarter: FY24Q3
Downstream Changes Summary:
  • Update the metadata handshake client.env.name field to optional.
  • Add client.env.container.
Engineering Lead: Kevin Albertson Kevin Albertson
Product Manager: Alex Bevilacqua Alex Bevilacqua
Program Manager: Esha Bhargava Esha Bhargava
Start date:
Scope Cost Estimate: 0
Cost to Date: 0
Final Cost Estimate: 0
Cost Threshold %: 100
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4684 Backlog
CXX-2715 Backlog
CSHARP-4718 Backlog
GODRIVER-2906 Fixed 1.13.0, 1.13.1
JAVA-5072 Fixed 5.0.0
NODE-5454 Backlog
MOTOR-1154 Duplicate
PYTHON-3837 Fixed 4.7
PHPLIB-1196 Blocked
RUBY-3298 Fixed 2.20.0
RUST-1703 Fixed 2.8.0

 Description   

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



 Comments   
Comment by Dan Mckean [ 06/Dec/23 ]

esha.bhargava@mongodb.com Wow, that's so much further along than I realised!

I thought we were starting with rust only. And I didn't even realise that had been done.

Do you know where/how I can access the data? Or can you suggest someone?

Comment by Dan Mckean [ 06/Dec/23 ]

Hi esha.bhargava@mongodb.com - is there any update to this? This work will be a massive benefit to our support of Kubernetes users and we're desperate to make use of the data from this!

Comment by Githook User [ 28/Aug/23 ]

Author:

{'name': 'Abraham Egnor', 'email': 'abraham.egnor@mongodb.com', 'username': 'abr-egn'}

Message: DRIVERS-2570 Report docker or kubernetes environment in handshake (#1454)
Branch: master
https://github.com/mongodb/specifications/commit/611ecb5d624708b81a4d96a16f98aa8f71fcc189

Comment by PM Bot [ 03/Apr/23 ]

Alex Bevilacqua renamed project from "Driver container awareness" to "Driver Container and Kubernetes Awareness"

Comment by Dan Mckean [ 20/Mar/23 ]

Oh great, I wasn't aware of that one, but yes, the needs are very aligned!

Let me know if anything is needed, but I agree that we can skip the PD

Comment by Dan Mckean [ 20/Mar/23 ]

alex.bevilacqua@mongodb.com I'm happy to draft a PD if the ask is unclear or needs more context.

Comment by Dan Mckean [ 17/Mar/23 ]

esha.bhargava@mongodb.com please let me know if you need anything to help progress this! It's really important for our team and others!

Comment by Dan Mckean [ 07/Mar/23 ]

CC felipe.munoz@mongodb.com regarding the conversation we had about wanting to ID microservices architecture customers.

Comment by Dan Mckean [ 07/Mar/23 ]

CC melissa.plunkett@mongodb.com

Generated at Thu Feb 08 08:25:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.