Elasticsearch
![Card image cap](https://stoeps.de/posts/2022/update-elasticsearch-certificates/renaldo-matamoro-WzgnhsodeqU-unsplash_hud151d2b86ef3afb45a13879274dc93cf_1584887_350x175_fill_q75_box_smart1.jpg)
Elasticsearch in HCL Connections Componentpack is secured with Searchguard and needs certificates to work properly. These certificates are generated by bootstrap during the initial container deployment with helm
.
These certificates are valid for 10 years (chain_ca.pem
) or 2 years (elasticsearch*.pem
) and stored in the Kubernetes secrets elasticsearch-secret
, elasticsearch-7-secret
. So when your HCL Connections deployment is running for 2 years, the certficates stop working.
![Card image cap](https://stoeps.de/posts/2022/backup-elasticsearch-indices-cronjob/jandira-sonnendeck-AcW1ZwD-qC0-unsplash_hu26d67ebfb66a91035cfd61679b5843cb_703344_350x175_fill_q75_box_smart1.jpg)
Last week I played around with the HCL Connections documentation to backup Elasticsearch in the article Backup Elasticsearch Indices in Component Pack .
In the end I found that I couldn’t get the snapshot restored and that I have to run a command outside of my Kubernetes cluster to get a snapshot on a daily basis. That’s not what I want.
![Card image cap](https://stoeps.de/posts/2022/backup-elasticsearch-indices/markus-winkler-cV9-hOgoaok-unsplash_hu04e9b688a6e7c4bd08c386f4d2166a8e_2922477_350x175_fill_q75_box_smart1.jpg)
During a migration from Cognos Metrics to Elasticsearch Metrics, I had some issues with the index. So I wanted to create a backup of the already migrated data and start over from scratch.
The official documentation has an article on the topic: Backing up and restoring data for Elasticsearch-based components , but I had to slightly adjust the commands to get a successful snapshot.
Last Update: Read in about 6 min