Dive FAQ

What is Dive?

Dive is a control plane for Kubernetes SREs and platform teams. It’s designed to give your team SRE superpowers by giving you a live view of all your application, where it’s deployed, and how it got to that state.

For example, Dive can build a map of services running across your clusters, how they’re related, where they’re deployed, what version of code is running, and so it. Dive can automatically tracks deploys, automatically monitor SLOs and other metadata, and much, much more.

Who made Dive?

Dive is made by your friends at Buoyant, the creators of Linkerd. Linkerd makes services on Kubernetes safe, reliable, and observable, and Dive extends those powers to the people and process side of the equation.

Is Dive free?

Dive is currently free while in private beta. In the future, we’ll introduce paid plans, most likely around the retention period for event data.

Does Dive require Linkerd?

Yes. Dive uses Linkerd to access service-level information not provided by Kubernetes, including traffic metrics, dependencies, TLS, and canary deploys. Luckily, Linkerd is easy to install and consumes minimal resources on your cluster.

How do I get access to Dive?

Fill out the waitlist form. We’ll contact you when you’re ready to use Dive!

Why does Dive require write access to my private GitHub repos?

Dive never modifies your GitHub repository data. Unfortunately (believe it or not) it is not possible to request read-only access to private GitHub repos. It’s all or nothing.

What does Dive do with GitHub repos anyways?

Dive pulls commit metadata from GitHub to provide smart summaries of what code went out in Kubernetes code rollouts. In the future, Dive will also allow you to describe service metadata, including descriptions, teams, and SLOs, directly in the repo for that service.

Does Dive expose my cluster or repo information to the public?

No. We take data security very seriously. Unless you explicitly tell it otherwise, Dive never exposes any cluster or repo information to anyone outside of your GitHub organization.

What if I don’t use GitHub?

We’ll add other SSO mechanisms soon. Add your voice to the feature requests!

Still have questions?