项目文件夹

文件
wehub-resource-sync e115934061
Publish `@librechat/data-schemas` to NPM / pack (push) Failing after 8s
Publish `@librechat/client` to NPM / pack (push) Failing after 0s
GitNexus Index / index (push) Failing after 1s
Sync Locize Translations & Create Translation PR / Create Translation PR on Version Published (push) Has been skipped
Sync Helm Chart Tags / Sync chart tags (push) Failing after 2s
Publish `librechat-data-provider` to NPM / pack (push) Failing after 1s
Docker Dev Images Build / build (Dockerfile, librechat-dev, node) (push) Failing after 1s
Docker Dev Images Build / build (Dockerfile.multi, librechat-dev-api, api-build) (push) Failing after 0s
Sync Helm Chart Tags / Ignore non-main push (push) Has been skipped
Sync Locize Translations & Create Translation PR / Sync Translation Keys with Locize (push) Failing after 1s
Publish `@librechat/client` to NPM / publish-npm (push) Has been cancelled
Publish `librechat-data-provider` to NPM / publish-npm (push) Has been cancelled
GitNexus Index / post-index (push) Has been cancelled
Publish `@librechat/data-schemas` to NPM / publish-npm (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:08:12 +08:00

43 行
1.2 KiB
YAML

# DNS Configuration Examples for LibreChat Helm Chart
# This file demonstrates how to configure custom DNS settings for traffic redirection
# Example 1: Redirect AWS Bedrock traffic to a proxy server
dnsPolicy: "None" # Ignore cluster DNS, use only custom DNS
dnsConfig:
nameservers:
- "10.0.0.10" # Your custom DNS server that handles redirections
- "8.8.8.8" # Fallback to Google DNS for other domains
searches:
- "svc.cluster.local"
- "cluster.local"
options:
- name: ndots
value: "2"
---
# Example 2: Use corporate DNS server
dnsPolicy: "None"
dnsConfig:
nameservers:
- "192.168.1.53" # Corporate DNS server
- "192.168.1.54" # Backup DNS server
---
# Example 3: Combine with hostAliases for simple redirects
dnsPolicy: "ClusterFirst" # Use cluster DNS first
dnsConfig:
options:
- name: timeout
value: "1"
- name: attempts
value: "2"
# Note: For simple host-to-IP mappings, you can also use hostAliases
# in combination with DNS configuration (add this to deployment spec):
# hostAliases:
# - ip: "10.100.50.200"
# hostnames:
# - "bedrock-runtime.us-east-1.amazonaws.com"
# - "api.openai.com"