-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
include sample for self-managed clusters (#31)
- Loading branch information
Showing
2 changed files
with
51 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
50 changes: 50 additions & 0 deletions
50
charts/deepgram-self-hosted/samples/03-basic-setup-onprem.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
# See the Chart [README](https://github.com/deepgram/self-hosted-resources/blob/main/charts/deepgram-self-hosted#values) | ||
# for documentation on all available options. | ||
|
||
global: | ||
# pullSecretRef should refer to a K8s secret that | ||
# must be created prior to installing this Chart. | ||
# Consult the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/secret/) for best practices on configuring Secrets for use in your cluster. | ||
# | ||
# You can create a secret for your image pull credentials | ||
# with the following commands: | ||
# ```bash | ||
# docker login quay.io | ||
# kubectl create secret generic dg-regcred \ | ||
# --from-file=.dockerconfigjson=$HOME/.docker/config.json \ | ||
# --type=kubernetes.io/dockerconfigjson | ||
# ``` | ||
pullSecretRef: "dg-regcred" | ||
|
||
# deepgramSecretRef should refer to a K8s secret that | ||
# must be created prior to installing this Chart. | ||
# Consult the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/secret/) for best practices on configuring Secrets for use in your cluster. | ||
# | ||
# You can create a secret for your Deepgram self-hosted API key | ||
# with the following command: | ||
# ```bash | ||
# kubectl create secret generic dg-self-hosted-api-key --from-literal=DEEPGRAM_API_KEY='<id>' | ||
# ``` | ||
deepgramSecretRef: "dg-self-hosted-api-key" | ||
|
||
scaling: | ||
replicas: | ||
api: 1 | ||
engine: 1 | ||
auto: | ||
# Most on-premises clusters will have a static number of servers, where autoscaling may not be desirable. | ||
enabled: false | ||
|
||
engine: | ||
modelManager: | ||
volumes: | ||
customVolumeClaim: | ||
enabled: true | ||
name: deepgram-models-pv # Replace with the name of the local PersistentVolume you have created | ||
modelsDirectory: "/" | ||
|
||
licenseProxy: | ||
enabled: true | ||
|
||
gpu-operator: | ||
enabled: true |