-
Notifications
You must be signed in to change notification settings - Fork 33
Expand file tree
/
Copy pathexample-values.yaml
More file actions
118 lines (106 loc) · 3.57 KB
/
Copy pathexample-values.yaml
File metadata and controls
118 lines (106 loc) · 3.57 KB
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
113
114
115
116
117
118
# If you need to update an image prior to release, we will have you uncomment and update the tag value.
# image:
# tag: 0.47.0
env:
# replace <your-model> with your LLM model and uncomment this variable
# LITELLM_DEFAULT_MODEL: "litellm_proxy/<your-model>"
ingress:
enabled: false
host: "app.example.com"
annotations:
{}
# Value should match your Issuer/ClusterIssuer and uncomment if you're using cert-manager for certificates
# cert-manager.io/cluster-issuer: letsencrypt
tls:
# requires cert for all enabled ingresses
enabled: true
github:
# Set this to true if you are using GitHub as your identity provider
enabled: false
gitlab:
# Set this to true if you are using GitLab as your identity provider
enabled: false
bitbucket:
# Set this to true if you are using BitBucket as your identity provider
enabled: false
keycloak:
enabled: true
ingress:
enabled: false
hostname: "auth.app.example.com"
annotations: {}
# Value should match your Issuer/ClusterIssuer and uncomment if you're using cert-manager for certificates
# cert-manager.io/cluster-issuer: letsencrypt
postgresql:
enabled: true
litellm:
# Set this to true if you are using your own litellm instance
#
# NOTE: We recommend using the provided LiteLLM instance for simplicity and
# because it is the most extensively tested scenario. Our automation uses an
# admin key to do user management for the LiteLLM instance.
enabled: true
url: "https://llm-proxy.example.com"
litellm-helm:
# Set this to false if you are using your own litellm instance
#
# NOTE: We recommend using the provided LiteLLM instance (enabled: true) for
# simplicity and because it is the most extensively tested scenario. Our
# automation uses an admin key to do user management for the LiteLLM instance.
enabled: true
ingress:
enabled: false
hosts:
- host: llm-proxy.example.com
paths:
- path: /
pathType: Prefix
tls:
- secretName: llm-proxy-tls
hosts:
- llm-proxy.example.com
proxy_config:
environment_variables:
{
"OR_APP_NAME": "OpenHands",
"OR_SITE_URL": "https://docs.all-hands.dev",
}
# Needs to be updated with your models. If you bring your own litellm, then
# just point at that!
#
# NOTE: We recommend using the provided LiteLLM instance for simplicity and
# because it is the most extensively tested scenario.
#
# model_list:
# - model_name: "prod/claude-3-5-sonnet-20241022"
# litellm_params:
# model: "anthropic/claude-3-5-sonnet-20241022"
# api_key: os.environ/ANTHROPIC_API_KEY
# - model_name: "prod/claude-3-7-sonnet-20250219"
# litellm_params:
# model: "anthropic/claude-3-7-sonnet-20250219"
# api_key: os.environ/ANTHROPIC_API_KEY
#
# Enable only when you trust callers and need custom x-* request headers
# forwarded to upstream LLM providers.
# general_settings:
# forward_client_headers_to_llm_api: true
runtime-api:
enabled: true
ingress:
enabled: false
host: runtime-api.example.com
annotations: {}
# Value should match your Issuer/ClusterIssuer and uncomment if you're using cert-manager for certificates
# cert-manager.io/cluster-issuer: letsencrypt
env:
RUNTIME_BASE_URL: "runtime.example.com"
# Set to storage class you want to use.
STORAGE_CLASS: "gp2"
sandbox:
apiHostname: https://runtime-api.example.com
# Tavily API for web search functionality (optional)
# tavily:
# enabled: true
# auth:
# existingSecret: tavily-api-key