When deploying Aspire in a Kubernetes cluster.
The current guide assumes that a Elasticsearch/Kibana services have already been deployed, and basic authentication is used.
See ECK quickstart on how to deploy Elasticsearch / Kibana on Kubernetes.
If using HTTPS on elasticsearch, make sure the certificate is signed by a Trusted CA, otherwise you would need to have access to its CA certificate, and import it into a JKS for Aspire to trust. See Enable HTTPS for instructions on how to import a certificate authority.
For AWS Elasticsearch configuration see Elasticsearch NoSQL Provider Properties.
(Skip these steps if you already have an Elasticsearch cluster for Aspire to use). The current guide is based on ECK quickstart
Install custom resource definitions
kubectl create -f https://download.elastic.co/downloads/eck/1.7.0/crds.yaml kubectl apply -f https://download.elastic.co/downloads/eck/1.7.0/operator.yaml
Create a file called elasticsearch.yaml
Deploy the Elasticsearch cluster
kubectl apply -f elasticsearch.yaml
The password will be stored in the environment variable called "PASSWORD"
PASSWORD=$(kubectl get secret quickstart-es-elastic-user -o go-template='{{.data.elastic | base64decode}}')
Create a file called kibana.yaml
Deploy Kibana
kubectl apply -f kibana.yaml
Expose Kibana's port locally
kubectl port-forward service/quickstart-kb-http 5601