For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Ask AIPlaygroundLoginFree API Key
HomeAPI ReferenceVoice AgentSpeech-to-TextText-to-SpeechIntelligenceSelf-Hosted Deployments
HomeAPI ReferenceVoice AgentSpeech-to-TextText-to-SpeechIntelligenceSelf-Hosted Deployments
    • Introduction
    • Deployment Environments
  • Amazon SageMaker
    • Deploy Deepgram on Amazon SageMaker
    • Requesting SageMaker Quota
    • Validate a Deepgram SageMaker Endpoint
    • Auto-Scaling SageMaker Endpoints
    • Configure Amazon SageMaker Deployments
    • Update an Amazon SageMaker Endpoint
    • Deploy with Terraform
    • Observability for Amazon SageMaker
    • Security and Compliance
  • Docker/Podman
    • Drivers and Container Orchestration Tools
  • Kubernetes
    • Securing Your Cluster
    • Troubleshooting
  • Deployment
    • Self Service Licensing & Credentials
    • Deploy STT Services
    • Deploy Flux Model (STT)
    • Deploy TTS Services
    • Deploy Voice Agent
    • Status Endpoint
    • Certificate Status
  • Partner Deployment
  • Scaling and Deployment Strategies
    • System Maintenance
    • Blue-Green Deployment
    • Auto-Scaling
    • Metrics Guide
    • Ingress Authentication
    • Redact Usage
    • Log Formats
    • Using Private Container Registries
  • Features
    • Smart Formatting
  • Self-Hosted Add Ons
    • License Proxy
    • Prometheus Integration
    • Deepgram UniMRCP Plugin
    • Using SDKs with Self-Hosted
LogoLogo
Ask AIPlaygroundLoginFree API Key
On this page
  • Secrets
Kubernetes

Securing Your Cluster

Deepgram strongly recommends regular reviews of the security posture of your self-hosted environment. In a Kubernetes context, this may include reviewing the of the official Kubernetes documentation, as well as any security guidance from your cloud provider.

Secrets

Deepgram strongly recommends following best practices for configuring Kubernetes Secrets. Resources offered by Deepgram assist your secrets security posture as follows:

  • The deepgram-self-hosted Helm chart includes options to configure RBAC rules for all resources.
  • Deepgram documentation instructs users to deploy Deepgram services in a dedicated namespace in your cluster.
    • This prevents workloads in other namespaces from reading Secrets intended for Deepgram-related resources, and restricts Deepgram-related resources from reading Secrets deployed in other namespaces in your cluster.
  • Deepgram documentation recommends using an external Secret store provider.
Was this page helpful?
Previous

Troubleshooting

If you encounter any challenges while deploying or maintaining your Deepgram self-hosted services on Kubernetes, please consult this guide.

Next
Built with