You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Architecture is a 3 node-sets clusters: master / data / client nodes. I want enable azureAD auth only on client nodes (because only client nodes are accessible). Auth OIDC requires HTTPS and specific secureSettings.
ECK operator take Elasticsearch CRD config to deploy a StatefulSet by nodeSet, who share secureSettings.
Feature
We must be able to add secureSettings by nodeSet.
Workaround
We can add an init container to add some secrets (inside Elasticsearch node spec):
initContainers:
- name: post-elastic-internal-init-keystoreimage: docker.elastic.co/elasticsearch/elasticsearch:8.8.1command:
- /usr/bin/env
- bash
- '-c'args:
- | # add all existing secret entries into it for filename in /mnt/elastic-internal/secure-settings/*; do [[ -e "$filename" ]] || continue # glob does not match key=$(basename "$filename") echo "Adding "$key" to the keystore." /usr/share/elasticsearch/bin/elasticsearch-keystore add-file "$key" "$filename" doneresources:
limits:
cpu: 500mmemory: 196Mirequests:
cpu: 500mmemory: 196MivolumeMounts:
- name: auth-azuread-secure-settingsmountPath: /mnt/elastic-internal/secure-settingsreadOnly: true
- name: elastic-internal-elasticsearch-config-localmountPath: /usr/share/elasticsearch/config
- name: elastic-internal-elasticsearch-configreadOnly: truemountPath: /mnt/elastic-internal/elasticsearch-configvolumes:
- name: auth-azuread-secure-settingssecret:
secretName: auth-azuread-secure-settingsdefaultMode: 420optional: false
(btw: I am not comfortable with ECK operator reading my secrets ...)
The text was updated successfully, but these errors were encountered:
Any security related configuration should alwasy be applied to all nodes in the cluster. If you want to restric external access to the coordinating-only nodes you should do this via other means (e.g. ingress)
Proposal
Use case. Why is this important?
Architecture is a 3 node-sets clusters: master / data / client nodes. I want enable azureAD auth only on client nodes (because only client nodes are accessible). Auth OIDC requires HTTPS and specific secureSettings.
ECK operator take
Elasticsearch
CRD config to deploy a StatefulSet by nodeSet, who sharesecureSettings
.Feature
We must be able to add secureSettings by nodeSet.
Workaround
We can add an init container to add some secrets (inside Elasticsearch node spec):
(btw: I am not comfortable with ECK operator reading my secrets ...)
The text was updated successfully, but these errors were encountered: