Artwork

Content provided by Data on Kubernetes Community. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Data on Kubernetes Community or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.
Player FM - Aplicație Podcast
Treceți offline cu aplicația Player FM !

Dok Talks #153 - CRD Panel // Eyar Zilberman & Álvaro Hernández

58:05
 
Distribuie
 

Manage episode 344159991 series 2865115
Content provided by Data on Kubernetes Community. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Data on Kubernetes Community or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.

https://go.dok.community/slack
https://dok.community

We are going to speak about CRDs, and discuss considering them as higher level entities that we normally consider them.

CRDs normally are kind of a byproduct of an operator. But in reality, they can be considered as the user-facing API of the operator surface. And as such, we would like to introduce conversations about even standardizing some of them, or creating "specifications" out of some CRDs.

Take this for example: there are some CRDs that could be, potentially, common across multiple operators. Think of a CRD to represent an S3 (or any other storage object) bucket. For operators that store data in object stores, each and every one of them are creating their own versions. But shouldn't we have some "standardized" `ObjectStorage` CRD, without a controller, that all could use?

We'll be joined by John Sanda of DataStax who works on the K8ssandra project, Alvaro Hernandez who is the CEO of Ongres and Postgres superhero, and Eyar Zilberman Co-Founder and Chief Product Officer at Datree.

  continue reading

243 episoade

Artwork
iconDistribuie
 
Manage episode 344159991 series 2865115
Content provided by Data on Kubernetes Community. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Data on Kubernetes Community or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ro.player.fm/legal.

https://go.dok.community/slack
https://dok.community

We are going to speak about CRDs, and discuss considering them as higher level entities that we normally consider them.

CRDs normally are kind of a byproduct of an operator. But in reality, they can be considered as the user-facing API of the operator surface. And as such, we would like to introduce conversations about even standardizing some of them, or creating "specifications" out of some CRDs.

Take this for example: there are some CRDs that could be, potentially, common across multiple operators. Think of a CRD to represent an S3 (or any other storage object) bucket. For operators that store data in object stores, each and every one of them are creating their own versions. But shouldn't we have some "standardized" `ObjectStorage` CRD, without a controller, that all could use?

We'll be joined by John Sanda of DataStax who works on the K8ssandra project, Alvaro Hernandez who is the CEO of Ongres and Postgres superhero, and Eyar Zilberman Co-Founder and Chief Product Officer at Datree.

  continue reading

243 episoade

Όλα τα επεισόδια

×
 
Loading …

Bun venit la Player FM!

Player FM scanează web-ul pentru podcast-uri de înaltă calitate pentru a vă putea bucura acum. Este cea mai bună aplicație pentru podcast și funcționează pe Android, iPhone și pe web. Înscrieți-vă pentru a sincroniza abonamentele pe toate dispozitivele.

 

Ghid rapid de referință

Listen to this show while you explore
Play