Skip to content

advanced_configuration.md

Latest commit

 

History

History
83 lines (60 loc) · 2.22 KB

advanced_configuration.md

File metadata and controls

83 lines (60 loc) · 2.22 KB

Advanced Configuration

Managing the Kubernetes cluster

If you would like to manage the Kubernetes cluster, you can use the kubectl command on the server, or download the kubeconfig file from the server and use it on your local machine.

scp -i my-key.pem ubuntu@<server-ip>:/home/ubuntu/.kube/config ~/.kube/config

Using Multiple Helm Values Files

The Galaxy deployment supports using multiple Helm values files, which allows you to compose configurations from different sources. This is useful for:

  • Separating base configuration from environment-specific overrides
  • Maintaining common settings across deployments
  • Adding optional features (like GCP Batch) via additional values files

Single Values File (Default)

By default, the playbook uses values/values.yml:

ansible-playbook -i inventories/vm.ini playbook.yml

You can specify a different single file:

ansible-playbook -i inventories/vm.ini playbook.yml \
  --extra-vars '{"galaxy_values_files": ["values/custom.yml"]}'

Multiple Values Files

To use multiple values files, pass a list to galaxy_values_files:

ansible-playbook -i inventories/vm.ini playbook.yml \
  --extra-vars '{"galaxy_values_files": ["values/values.yml", "values/gcp-batch.yml"]}'

Or using JSON syntax:

ansible-playbook -i inventories/vm.ini playbook.yml \
  -e galaxy_values_files='["values/base.yml","values/prod.yml"]'

Files are applied in order, with later files overriding earlier ones (following Helm's standard behavior).

Example: Composing Configurations

Create separate values files for different purposes:

# values/base.yml - Common settings
persistence:
  size: "20Gi"
postgresql:
  galaxyDatabasePassword: "changeme"

# values/production.yml - Production-specific settings
persistence:
  size: "100Gi"
configs:
  galaxy.yml:
    galaxy:
      admin_users: "admin@example.com"

# values/gcp-batch.yml - GCP Batch job runner
configs:
  job_conf.yml:
    runners:
      gcp_batch:
        load: galaxy.jobs.runners.gcp_batch:GCPBatchJobRunner

Then deploy with:

ansible-playbook -i inventories/vm.ini playbook.yml \
  -e galaxy_values_files='["values/base.yml","values/production.yml","values/gcp-batch.yml"]'