Feature #13650

[DOC] document arvados-kubernetes

Added by Ward Vandewege over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-
Release:
Release relationship:
Auto

Associated revisions

Revision 6adfd4dc (diff)
Added by Ward Vandewege over 2 years ago

Add basic documentation for the new Arvados on Kubernetes install option.

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision 478e1810 (diff)
Added by Ward Vandewege over 2 years ago

Add basic documentation for the new Arvados on Kubernetes install option.

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision 43d3cb88 (diff)
Added by Ward Vandewege over 2 years ago

A series of documentation improvements based on review feedback.

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision 0c8e5222
Added by Ward Vandewege over 2 years ago

13650: Merge branch 'master' into 13650-document-arvados-kubernetes

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision 945258f2 (diff)
Added by Ward Vandewege over 2 years ago

Add basic documentation for the new Arvados on Kubernetes install option.

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision ba908bbe (diff)
Added by Ward Vandewege over 2 years ago

A series of documentation improvements based on review feedback.

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision a4ea4060
Added by Ward Vandewege over 2 years ago

13650: Merge branch '13650-document-arvados-kubernetes'

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision c90adfb6 (diff)
Added by Ward Vandewege over 2 years ago

Further doc improvements for Arvados on Kubernetes.

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision b004059a
Added by Ward Vandewege over 2 years ago

13650: Merge branch '13650-document-arvados-kubernetes'

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

Revision edf5021c (diff)
Added by Ward Vandewege over 2 years ago

Minikube is not supported yet by our Arvados on Kubernetes Helm Chart.

refs #13650

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

History

#1 Updated by Ward Vandewege over 2 years ago

  • Status changed from New to In Progress

#2 Updated by Ward Vandewege over 2 years ago

Ready for initial review @commit:478e1810

#3 Updated by Peter Amstutz over 2 years ago

Install options chart

  • Are we still using "Curoverse" branding for the Arvados support subscription, there's been some ongoing confusion that "Curoverse" now refers to Curoverse Research?
  • The "Demo" column is all "yes" so I don't think it contributes anything
  • Don't understand the difference is between "Workflow Development" and "Workflow QA/QC" columns.
  • "Arvados Software Development" column header is sort of ambiguous, maybe call it "Developing Arvados" ?
  • The last row for "Cluster operations subscription" should be all "yes" even if the last two columns don't totally make sense

2 While Arvados on Kubernetes is not yet ready for production use, it is being developed toward that goal

Suggest:

2 Arvados on Kubernetes is under development and not yet ready for production use

Arvados on Kubernetes

Reminder that in textile you need to use @-signs around quoted code, not backticks.

If that does not describe your environment, please see the "GKE":#GKE or "Minikube":#Minikube sections below to get set up with Kubernetes."

How about

If you do not have a Kubernetes cluster already set up, you can use "Minikube":#Minikube for single node development and testing, "Google Kubernetes Engine":#GKE at scale, or another Kubernetes solution.

Maybe move the GKE and Minikube instructions to their own pages?

The "Install helm" section is missing a link to instructions to actually install helm (now I see it's down in the GKE/Minikube install sections, but I don't know if that's the right place for it.)

"determine the IP address..." can that be any more specific, is there a "kubectl" command to figure it out? It looks like the GKE instructions include getting the IP, but not the Minikube ones.

#4 Updated by Ward Vandewege over 2 years ago

  • Status changed from In Progress to Resolved
  • Target version set to 2018-07-03 Sprint

Thanks Peter, I've revised the text and merged the branch.

#5 Updated by Tom Morris over 2 years ago

  • Release set to 13

Also available in: Atom PDF