Recipes
Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECK
Generally available
This section includes recipes that provide configuration examples for some common use cases.
- Expose Elasticsearch and Kibana using a Google Cloud Load Balancer (GCLB)
- Expose Elasticsearch and Kibana using Istio ingress gateway
- Using Logstash with ECK
- Expose Elastic Maps Server and Kibana using a Kubernetes Ingress
- Secure your cluster with Pod Security Policies
- Use Traefik to expose Elastic Stack applications
- Deploy Elasticsearch, Kibana, Elastic Fleet Server and Elastic Agent within GKE Autopilot
Compared to other configuration examples that are consistently tested, like fleet-managed Elastic Agent on ECK, standalone Elastic Agent on ECK, or Beats on ECK, the recipes in this section are not regularly tested by our automation system, and therefore should not be considered to be production-ready.
Ingress is a standard Kubernetes concept. While ECK-managed workloads can be publicly exposed using ingress resources, and we provide example configurations, setting up an Ingress controller requires in-house Kubernetes expertise.
If ingress configuration is challenging or unsupported in your environment, consider using standard LoadBalancer services as a simpler alternative.