Deploying a scalable, resilient video streaming infrastructure can be a daunting task — but it doesn’t have to be. Google Kubernetes Engine (GKE) offers a fully managed Kubernetes environment that simplifies container orchestration, auto-scaling, and service reliability, making it a perfect match for modern streaming workloads.
In this guide, we walk you through how to deploy Ant Media Server — a powerful real-time streaming solution supporting WebRTC, HLS, LL-HLS, and more — on GKE with minimal effort. Using Helm charts, you can automate deployment and configuration of cluster resources such as origin and edge instances, Ingress, and certificates, reducing manual setup and operational overhead.
By the end of this tutorial, you’ll have a fully functional Ant Media Server cluster running on GKE, ready to handle large-scale live streaming with reliability and ease. Whether you’re building interactive apps, global broadcasts, or ultra-low latency workflows, this approach provides a cloud-native foundation that grows with your needs.
Table of Contents
Prerequisites
Before diving in, ensure you have the following tools ready:
Creating Your Google Kubernetes Engine Cluster
Let’s kick off by setting up a Google Kubernetes Engine cluster.
- Navigate to your Google Cloud console.
- Activate the Kubernetes Engine service if not active already, then click the Create button.
- Navigate to Kubernetes Engine and select SWITCH TO STANDARD CLUSTER.
- Configure cluster details such as Zone, Name, and Kubernetes version, then proceed to the Nodes tab.
- Choose a compute-optimized instance type like the c2-standard-4 node type.
- Ensure the Public Cluster is selected in the Networking tab, adjust other settings as needed, and click Create to complete the cluster setup.
Connecting to Your Google Kubernetes Engine Cluster
Now that the cluster is up, let’s establish a connection using the Google SDK.
Run the following command:
gcloud container clusters get-credentials YOUR_CLUSTER_NAME --zone YOUR_ZONE --project YOUR_PROJECT_ID
Replace placeholders with your actual cluster name, zone, and project ID. For example:
gcloud container clusters get-credentials ams-gke-cluster --zone us-central1-c --project antmedia-public-385620
Note: Check these instructions to learn more about how to connect to your Google Kubernetes Engine cluster.
Installing Ant Media Server Cluster
Now that the Kubernetes cluster is created, it’s time to deploy the Ant Media Server onto our GKE cluster, effortlessly using Helm.
- Add the Ant Media repository to Helm:
helm repo add antmedia https://ant-media.github.io/helm
helm repo update- Set up your cluster using Helm, specifying the required parameters:
helm install antmedia antmedia/antmedia \
--set origin={origin}.{example.com} \
--set edge={edge}.{example.com} \
--set UseGlobalIP=false \
--set licenseKey="YOUR_LICENSE_KEY" \
--namespace antmedia \
--create-namespaceNote: For other parameters, please visit here.
If successful, you’ll see the public IP address/domain name in the output of kubectl get ingress command.
- After DNS registration, you can enable SSL and access your Ant Media Server GKE cluster.
Congratulations! You’ve successfully deployed the Ant Media Server cluster on the Google Kubernetes Engine using Helm. Now, you’re ready to publish and play!
WebRTC Publish and Play
Now that your AMS is deployed and ready, let’s publish a WebRTC stream following the Publish Live Stream instructions using the sample page.
Now that your WebRTC stream is publishing, let’s play the stream 🙂
Frequently Asked Questions
What benefits does GKE provide for Ant Media Server deployments?
GKE offers managed Kubernetes, automated scaling, built-in security, and integration with Google Cloud tools — streamlining the deployment and operation of Ant Media Server clusters on the cloud.
Do I need Helm to deploy Ant Media Server on GKE?
Using Helm simplifies deployment by packaging all required Kubernetes manifests (Deployments, Services, Ingress, etc.) and makes configuration easy with a single install command.
Can I enable SSL for Ant Media Server running on GKE?
Yes — after DNS configuration, you can enable SSL by applying a certificate (self-signed or from a CA like Let’s Encrypt) to your Ingress resources for secure HTTPS streaming.
Is this setup suitable for production use and scaling?
Yes. With Kubernetes autoscaling and managed infrastructure from GKE, this deployment is production-ready and capable of handling high concurrency and dynamic streaming workloads.
Conclusion
In this guide, we’ve elucidated the process of configuring a Google Kubernetes Engine cluster and learned how to install the Ant Media Server using a Helm chart. By following these steps, you can ensure efficient content delivery to your audience, enhancing your real-time streaming experience with the power of GKE and AMS.
If you have questions or need support, please contact us via our form, schedule a meeting to chat over coffee, or write directly to [email protected] so we can work together to democratize live streaming.
