Skip these steps if you already have an Elasticsearch cluster for Aspire to use and go directly to Deploying Aspire 5.
The guide below is based on ECK quickstart. If you need a production deployment or a more detailed process description, please refer to:
Install custom resource definitions
Create a file called elasticsearch.yaml
Deploy the Elasticsearch cluster
The password will be stored in the environment variable called "PASSWORD"
Create a file called kibana.yaml
Expose Kibana's port locally
(Optional) Upload Kibana Dashboards
Kibana's port should be forwarded into localhost:5601 as of Step #6 on the Elasticsearch deployment instructions
The environment variable $PASSWORD should hold the elastic's user password as of Step #3 on the Elasticsearch deployment instructions.
Replace <EMAIL> and <PASSWORD> with your registered email and password
Create a file called aspire-config.yaml
The com_accenture_aspire_ssl_trustAll is not recommended to be set as true in production environments, the recommended way is to import the untrusted certificate into a Java Key Store (see Configuring a Certificate Store) and then importing using the com_accenture_aspire_ssl_truststore_file property (see SSL Certificates Properties).
Create a secret containing your settings.json and AspireLicense.lic files
Create a file called aspire-upload-job.yaml
When using a non local kubernetes cluster, make sure to change the image url to where the images are hosted.
Wait until it has uploaded the files
Create a random 32 bytes file which will be your key
Create the secret using the encryption.key file
Create Kubernetes ConfigMap holding the CA and Java Keystore with the certificate for the Aspire servers
Create a file called aspire-managers.yaml
Create a file called aspire-workers.yaml
Expose Manager port