forked from elixir-cloud-aai/TESK
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvalues.yaml
112 lines (101 loc) · 4.22 KB
/
values.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
# Default values for tesk.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
# host_name: tes.tsi.ebi.ac.uk
host_name: "tesktest.genx.link"
# There are two options here: "openshift" or "kubernetes"
clusterType: kubernetes
#
#
#
# 'openstack' or 's3'
storage: none
# Configurable storage class.
storageClass:
tesk:
# if empty - default base path; currently /ga4gh/tes/v1
#tes_api_base_path:
# For backwards compatibility with TES 0.3 - old base bath
tes_api_base_path: /ga4gh/tes/v1
image: docker.io/elixircloud/tesk-api:1.1.0
port: 8080
taskmaster_image_name: docker.io/elixircloud/tesk-core-taskmaster
taskmaster_image_version: v0.10.1
taskmaster_filer_image_name: docker.io/elixircloud/tesk-core-filer
taskmaster_filer_image_version: v0.10.1
debug: true
executor_retries: 2
filer_retries: 2
transfer:
# If you want local file systems support (i.e. 'file:' urls in inputs and outputs),
# you have to define these 2 properties.
active: false
# wes_base_path: '/data' # WesElixir via docker-compose
wes_base_path: '/tmp' # WesElixir locally
# Change the value of $wesBasePath in minikubeStart accordingly
tes_base_path: '/transfer'
pvc_name: 'transfer-pvc'
auth:
# the following variables are specific to each deployment
# mode: auth/noauth
mode: noauth
# EBI/CSC
env_subgroup: CSC
env_basegroup: ECP_CLN
service:
# the following variables are specific to each deployment
# use:
# - NodePort, if you want to expose API directly
# - LoadBalancer for cloud provider (gcloud) or empty otherwise
# type: NodePort
# node_port: 31567
type: "LoadBalancer"
#node_port: ""
ftp:
# If you need FTP configuration, choose one of the 2 methods of providing credentials
classic_ftp_secret: ftp-secret
#netrc_secret:
#classic_ftp_secret:
#netrc_secret: netrc-secret
# If you install FTP locally, but outside of k8s and need a DNS entry for it (because your workflow manager might not like the IP address)
# one way of getting a DNS entry for your FTP service is to use a k8s "service without a selector"
# Put the IP under which your pods see see services running on your host (differs depending on the way you installes K8s)
# For virtualBox, it is 192.168.99.1 and your ftp service will be visible under ftp name
# You will be able to use it like this: ftp://ftp/file
#hostip:
#
# Configure this, only if you choose "kubernetes" as "clusterTYpe"
#
ingress:
active: true
# The path, where TESK API will be exposed.
# path: /tes
path: /
# If no TLS secret name configured, TLS will be switched off
tls_secret_name:
# Annotations for Ingress Resource.
annotations:
kubernetes.io/ingress.class: nginx
kubernetes.io/tls-acme: "true"
# Choose one of the following depending on your setup
# cert-manager.io/issuer: letsencrypt-production
cert-manager.io/cluster-issuer: letsencrypt-production
deploy_ingress:
# This provides installation of one specific Ingress Controller https://github.com/nginxinc/kubernetes-ingress
# You will most probably be better off installing one of your choice yourself, as we may not update this section frequently enough.
# Also it is likely the installation of an Ingress Controller will be removed completely from the chart
active: true
nginx_image: nginx/nginx-ingress:1.4.6
# the following variables are specific to each deployment
# We used externalIP to expose Ingress on 80/443 port. On OpenStack internal IP of master node (10.*) worked for us.
# Could be any node, but calls to the service have to be using it. In our case DNS entry is assigned to master's external IP
# Use NodePort as an alternative (breaks Swagger)
external_ip: 10.9.0.4
node_port: 30977
# the following variables are specific to each deployment
# use:
# - scope=Cluster, if you want Ingress to listen to all namespaces (requires ClusterAdmin)
# - scope= , if you want Ingress to listen only to its own namespace
scope: "Cluster"
#
#