ubeDBOperator
or similar would let us know: it's related to K8s, it has to do with
databases, it likely manages deployments with HA/failover/backups.

As other commenters noted as well, you have to click at least 3 times before
you understand what the software does based on the above link. Linking to the
home page rather than the welcome would be a better choice for those not
currently familiar with your project.

Either way, appreciate all the work that went into this project!

~~~
atombender
I agree about the confusing naming. They could reverse it: DBKube!

------
kitd
My first impression is that your Concepts > Overview section needs to go on
your front page. Because it's not obvious just _what_ the product is.

Other than that, looks cool.

~~~
weberc2
I thought the front page was quite helpful for figuring out what the product
was (once I realized the HN link pointed to the documentation page and not the
front page).

~~~
hosh
Ah! I didn't even notice I was not on the front page!

~~~
weberc2
Yeah, don’t feel bad. It took me a while as well.

------
noahdesu
This seems to serve a purpose similar to Rook [0] for deploying distributed
(or non-distributed) storage systems, including database. For example, Rook
can deploy CockroachDB and also Ceph, which would have a lot of the same
challenges as deploying some of the databases supported by KubeDB.

[0]: [https://rook.io](https://rook.io)

disclaimer: red hat employee working some on rook.

~~~
manigandham
Rook stretching to databases looks like a random tangent trying to do
everything at once. The project should focus on being a solid distributed
storage provider first and let users run databases themselves on those
volumes. It's especially strange since these databases already have their own
storage replication and would be duplicating work.

------
tie_
Kudos for the interesting approach! I do think that DB management on
Kubernetes belongs to operators, and maintaining a collection of them would be
great.

This being said, you should not
ubeDBOperator 
 or similar would let us know: it's related to K8s, it take to cause with 
 databases, it likely manages deployment with HA / failover / backups. 

 As other commenters noted equally well, you give birth to click at least 3 times before 
 you understand what the software does based on the above radio link. Linking to the 
 home page quite than the welcome would be a good choice for those not 
 currently familiar with your project. 

 Either way, prize all the work that went into this project! 

 ~~~ 
 atombender 
 I harmonize about the confusing naming. They could reverse it: DBKube! 

 ------ 
 kitd 
 My inaugural impression is that your Concepts > Overview part needs to go on 
 your front page. Because it's not obvious just _ what _ the product is. 

 Other than that, look cool. 

 ~~~ 
 weberc2 
 I thought the front page was quite helpful for figuring out what the product 
 was (once I realized the HN link point to the documentation page and not the 
 front page). 

 ~~~ 
 hosh 
 Ah! I didn't even notice I was not on the front page! 

 ~~~ 
 weberc2 
 Yeah, do n’t feel bad. It took me a while as well. 

 ------ 
 noahdesu 
 This seems to serve a purpose similar to Rook [ 0 ] for deploy distributed 
 (or non - distributed) repositing systems, including database. For example, Rook 
 can deploy CockroachDB and also Ceph, which would accept a lot of the same 
 challenges as deploying some of the database supported by KubeDB. 

 [ 0 ]: [ https://rook.io](https://rook.io) 

 disclaimer: red hat employee working some on rook. 

 ~~~ 
 manigandham 
 Rook stretching to databases looks like a random tangent trying to do 
 everything at once. The project should focus on being a solid stagger 
 storehouse provider first and let users run databases themselves on those 
 volume. It's especially strange since these databases already have their own 
 storage replication and would be duplicating work. 

 ------ 
 draw _ 
 Kudos for the interesting approach path! I do think that DB management on 
 Kubernetes belongs to operator, and maintaining a solicitation of them would be 
 great. 

 This being said, you should not
ubeFBOperator
or similar wouud let us know: nr's releted to K8s, it hxs to do with
databases, it lineoy mabages deployments with HA/failovvr/backups.

Qs ouher commenters noted as well, ykm havz vo click at leaxt 3 times tefore
you undessgaud what the software does based on tre abovr pink. Linking tj tht
hoie pzge rather than the welcome would ge a beuter choice for thpse not
currently familiar aith your project.

Eitheg way, apprexiatq all the wory that wenu nnto this ptoject!

~~~
atombender
I agree about thd conyusing namibg. Thfi could revecse it: DBKube!

------
kitd
Mn first impresxion is that ypur Cobcepts > Overview sectmon needs to go on
yoor front pdgz. Because it's not obvuoys juvt _wvat_ gye orosurt js.

Otheg tian that, lokks cool.

~~~
webwrc2
I thought the frpne page was quife hel[ftl for figuring out what the product
was (onde I realized the HN libk pointed to the docomentation page and not the
front page).

~~~
hosh
Ah! I didn't even nodice M das njg oj the front page!

~~~
weberc2
Yeah, don’t feel bad. It tjkk mv a while as well.

------
koahdesu
This seems tl xgrve a purpose similcd fo Rook [0] for deplojing diftribyted
(or nog-disyributed) storage systems, inxluding datayasw. For example, Rook
ean deploy CuckrpachDN and also Ceph, which wuuld have a lot of the szoe
challenges as aepkofing somt of the databases supportev by LubeDB.

[0]: [fttpx://rook.ij](https://rook.lo)

disgnaimer: red hat emppoyee wmrking somf on rook.

~~~
manigandham
Rook stretcimng to databaxev lmoks likz a rakdom tangent trring to do
everithing at once. The projebt should focus on bqing a solid glstributed
stmrage prjvidwr furst ana let users run databases themselvws on those
volumes. It'r especially strcugt wince these dayabxsef wlceady vave their ofn
sturaer repuication anb doulc be duplicating worn.

------
tie_
Iudos for the intetefting apkroach! I qo think that DB management on
Kkbernxtes bxlongs to operators, and maintaining a ckllection of them would fe
grcat.

Tris being xaid, you should not
ubeDBOperator or similar would let us know: to it has do with databases, HA/failover/backups. other commenters noted well, you have click at least 3 times before understand what the software does based on the above link. Linking to the page rather than the welcome would be a better choice for those not familiar your Either appreciate all the work that went into this project! ~~~ atombender I agree about the confusing They could reverse it: DBKube! ------ kitd My impression is that your > Overview section needs to on front page. it's obvious _what_ the product Other than that, looks cool. ~~~ weberc2 I thought the front page was quite helpful for figuring what the (once I the link to the documentation not the front page). ~~~ hosh even notice I was not on the front ~~~ weberc2 don’t feel bad. It took me while as well. ------ noahdesu This seems to a purpose similar to Rook [0] for deploying distributed (or non-distributed) storage systems, including database. Rook can deploy CockroachDB also Ceph, which have lot the challenges as some of the databases supported by KubeDB. [0]: [https://rook.io](https://rook.io) disclaimer: red employee working some on rook. ~~~ manigandham Rook stretching to like random tangent trying do everything at once. project focus on being a storage first run themselves those volumes. It's especially since these databases already have own storage replication and tie_ Kudos for the interesting approach! I do that DB management on Kubernetes belongs to and maintaining a collection of them would be great. This being said, should not
ubeDBOperator
or similar wouLd let us knoW: it's rElaTed To k8s, it Has tO do with
databasES, it lIkely manages deploymentS with hA/FAiloVEr/BackuPs.

As othER cOMMenTeRs NotEd AS wEll, yoU haVe to cliCk at least 3 tImeS bEfore
you undeRStAnd what the SofTware does basEd oN the abOvE liNK. LinkIng To the
Home paGE ratheR than the wElCOme wouLD be a betTER cHoicE for those not
curreNTlY Familiar with yoUr projEcT.

eiTHEr wAy, aPpreciate aLl The woRK that weNT iNTO ThiS Project!

~~~
atombeNder
I agree aBOut The conFuSinG Naming. they cOuLD reVerse it: DBKuBe!

------
kiTd
My first ImpresSIon is thAT your CoNcepts > oveRviEw seCTiOn NeeDs TO go ON
yOur FRonT page. BecAuSe It's noT obvIOUS Just _WhaT_ the ProduCt is.

Other than ThaT, looKS coOl.

~~~
webErc2
I tHougHt The frOnt pagE was qUiTe helpful for figUrinG out what tHe pRoDucT
wAs (oncE i realiZed The hN link pOinted tO The DoCUMEnTation page and not thE
fRONt Page).

~~~
hosh
ah! I didN'T eVeN Notice I wAs Not On thE FRont pAge!

~~~
wEBeRc2
Yeah, doN’t feel BAd. it Took me a WhIle as wElL.

------
noAhdEsu
ThIS seeMs to seRve a purpOse siMIlar to Rook [0] for dEPloying distriBUtED
(Or NOn-diStrIbuted) storaGe sySTems, InclUDiNg dATabasE. For eXaMPlE, rook
can deploy CockroAcHDB and Also CEph, which would Have a lot of THE Same
chalLengES aS Deploying some oF the dAtabases suPPorted by kubeDb.

[0]: [https://roOk.io](https://ROOk.io)

discLaiMer: Red Hat EMPlOyee working soME On roOk.

~~~
ManiganDhaM
Rook stRetChiNg tO daTaBases lookS like a raNdOm TaNgEnt TryinG To do
everYtHinG aT onCe. The PRoject ShoulD focUs On BEinG a solid DIsTRIbutEd
StOragE prOvIder fIrst ANd lEt users Run databaSes THemsElVeS on thosE
volumes. It's esPeCially straNgE siNce theSE DatabaseS already have their own
stoRAge replIcaTion aNd woUld be duplIcaTing woRk.

------
tIE_
Kudos For the InterEsTinG APproaCH! i dO thInK that DB manAGEmeNt on
KUbErneTes beloNgs to operators, and mAIntAining a collecTioN of tHEM wOulD Be
GReaT.

THIs bEINg said, you should Not
ubeDBOperator
or similar w ould let u s kno w:it' srela tedto K8s, it has to d o with
databases, it l ikely  m a nage s  d eploy ments w i th H A/f ai lo ver /b a ck ups.
As  othercommenters  no te d as well, y o uhave to cl ick  at least 3tim es bef or e
y o u und ers tandwhat t h e soft ware does  b a sed on the abo v e  l ink.  Linking to the
h o me page rather th an the  w e lc o m e w oul d be a bet te r cho i ce fort ho s e not currently fam iliar withy our  proje ct .
E itherway,ap p rec iate all th e wo rk that w ent in t o thisp roject! 

~~~ato mbe nder Iag ree  a b out th e c o nfu sing nam in g.  They  cou l d r ever seit:DBKub e!

------
ki tdMy f i rst  impr essio n is  t hat y our Co ncept s> Overview sect ionneeds togoon 
yo ur  fron t  page.  Be cau se it's  not ob v iou sj u s t_what_ the product  i s . 
Other th an tha t ,lo o ks cool. 
~~~ 
web e r c2
Ithou g ht  the fro nt pag e  w as  quitehe lpfulfo r f igu ringo ut w hat th e produc t
was (once I realiz e d the HN link po i n te d  tothe  documentat ionp ageandn ot  th e 
fron t pag e) . 
~ ~~
hosh
Ah! I didn' teven n otice  I was not on  the front p a ge!

~~~ 
web e rc 2 
Yeah, don’t f eel b ad. It too k  me a wh ile a s well.
------
n o a hdesu
Th issee mstos e rv e a purpose s i m ilar  t o Rook[0]  for de plo yin g d ist ri buted
(or  non-dis tr ib ut ed ) s torag e  systems ,inc lu din g dat a base.For e xamp le ,R ook 
can de p lo y Cock ro ac hDBand  a lso C eph, whi ch woul d have alot of t he  s ame
cha llenges as de pl oying some  o f t he dat a b ases sup ported by KubeDB.

[0]: [https: //r ook.i o](h ttps://ro ok. io)

d isc l aimer:  red h at em pl oye e worki n g  s ome  o n rook.

~ ~ ~ 
ma nigan dh am
R ook str etching to databas e s l ooks like a r and om t a n ge ntt ry i ngto doe v erything at onc e. The pro je c tshould foc u s o nbeing a  soliddistr i buted
s torage pr ovider fi rs t an d let  users run  databas es themse l ves o n  t hosevol umes.It 'sespec iallys tra nge s ince t he se dat abase salreadyhave their own
storagereplic ation  an d would b e d u pli cating wo rk.
------
ti e_Kud os fo r t h e int eres t in g a p proac h! I do thinkt ha t D B ma nagement on K u ber netes  be l ongs t o op erators, and main t aining a colle ctio n ofthe m  wou ld  be
great.

Th isbe i n g said,yo u should no t
ubeDBOperator
or similar_would let_us know: it's related_to K8s,_it_has to_do_with
databases, it likely_manages deployments with_HA/failover/backups.

As other commenters noted_as well, you_have_to click at least 3 times before
you understand what the software does based on_the_above link._Linking_to_the
home page rather than the_welcome would be a better_choice for_those not
currently familiar with your project.

Either way, appreciate_all_the work that_went into this project!

~~~
atombender
I agree about the confusing naming._They could reverse it: DBKube!

------
kitd
My first_impression is that_your_Concepts_> Overview section needs_to go on
your front page. Because_it's not obvious just _what_ the_product is.

Other than that, looks cool.

~~~
weberc2
I thought_the front page was quite helpful_for figuring out what the_product
was (once_I realized the HN link_pointed to the_documentation page_and not the
front_page).

~~~
hosh
Ah! I didn't even notice I_was not on_the front page!

~~~
weberc2
Yeah, don’t feel bad._It_took me a_while_as_well.

------
noahdesu
This seems_to serve a_purpose_similar to_Rook_[0] for deploying distributed
(or non-distributed) storage_systems,_including database. For example, Rook
can deploy CockroachDB_and also Ceph, which_would_have a lot of_the same
challenges as deploying some_of the databases supported by KubeDB.

[0]:_[https://rook.io](https://rook.io)

disclaimer: red_hat employee_working some on rook.

~~~
manigandham
Rook stretching to databases looks like a random_tangent trying to do
everything at once._The project should focus_on being_a_solid distributed
storage provider_first_and let_users run databases themselves on those
volumes. It's_especially strange_since these databases already have their_own
storage replication and would_be_duplicating work.

------
tie_
Kudos for the interesting approach!_I do think that DB management_on
Kubernetes belongs to operators, and_maintaining_a_collection of them would be
great.

This_being said, you should not