Arvados™ Docs
WARNING - you are viewing the documentation for an old version of Arvados. For the latest version, click here.
  1. Overview
    1. Installation options
  2. Docker quick start
    1. Arvados-in-a-box
  3. Arvados on Kubernetes
    1. Arvados on Kubernetes
    2. Arvados on Minikube
    3. Arvados on GKE
  4. Manual installation
    1. Planning and prerequisites
    2. Arvados package repositories
    3. Upgrading Arvados and Release notes
  5. Configuration
    1. Configuration files
    2. Migrating Configuration from v1.4 to v2.0
    3. Configuration reference
  6. Core
    1. Install API server and Controller
  7. Keep
    1. Install Keepstore servers
    2. Configure filesystem storage
    3. Configure S3 object storage
    4. Configure Azure Blob storage
    5. Install Keepproxy server
    6. Install Keep-web server
    7. Install Keep-balance
  8. User interface
    1. Set up web based login
    2. Install the Single Sign On (SSO) server
    3. Install Workbench
    4. Install Workbench 2
    5. Install Composer
  9. Additional services
    1. Install the websocket server
    2. Install the Git server
    3. Set up a shell node
    4. Configure webshell
  10. Containers API
    1. Set up a compute node
    2. Install arvados/jobs image
    3. Install the cloud dispatcher
    4. Install the SLURM dispatcher
    5. Test SLURM dispatch
  11. External dependencies
    1. Install PostgreSQL 9.4+
    2. Install Ruby and Bundler
    3. Install Nginx
    4. Setting up Google auth
    5. Set up Docker

Arvados on Kubernetes

Arvados on Kubernetes is implemented as a Helm 3 chart.

Note:

This Helm chart does not retain any state after it is deleted. An Arvados cluster created with this Helm chart is entirely ephemeral, and all data stored on the cluster will be deleted when it is shut down. This will be fixed in a future version.

Overview

This Helm chart provides a basic, small Arvados cluster.

Current limitations, to be addressed in the future:

  • An Arvados cluster created with this Helm chart is entirely ephemeral, and all data stored on the cluster will be deleted when it is shut down.
  • No dynamic scaling of compute nodes (but you can adjust values.yaml and reload the Helm chart)
  • All compute nodes are the same size
  • Compute nodes have no cpu/memory/disk constraints yet
  • No git server

Requirements

  • Minikube or Google Kubernetes Engine (Kubernetes 1.10+ with at least 3 nodes, 2+ cores per node)
  • kubectl and Helm 3 installed locally, and able to connect to your Kubernetes cluster

Please refer to Arvados on Minikube or Arvados on GKE for detailed installation instructions.

Previous: Arvados-in-a-box Next: Arvados on Minikube

The content of this documentation is licensed under the Creative Commons Attribution-Share Alike 3.0 United States licence.
Code samples in this documentation are licensed under the Apache License, Version 2.0.