Chris Denneen cdenneen
reyjrar
/ elasticsearch.yml
Last active
May 12, 2023 11:58
ElasticSearch config for a write-heavy cluster
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ################################################################## | |
| # /etc/elasticsearch/elasticsearch.yml | |
| # | |
| # Base configuration for a write heavy cluster | |
| # | |
| # Cluster / Node Basics | |
| cluster.name: logng | |
| # Node can have abritrary attributes we can use for routing |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| I had a bit of trouble figuring out how to use bitnami's [sealed secrets](https://github.com/bitnami-labs/sealed-secrets) with [helm](https://helm.sh) | |
| Here's a definition of done to help you see what I was trying to achieve. | |
| **Definition of done** | |
| - Single secret available for a release in a namespace, listing all secret variables | |
| - Regular helm workflow, with no extra kubeseal commands for developers | |
| - Encrypted secrets clearly visible in git | |
| - Sealedsecret managed by helm |