-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OPSEXP-2950 Prepare to update to Elasticsearch 8 by switching to the bitnami/elasticsearch chart #1267
base: master
Are you sure you want to change the base?
Conversation
helm/alfresco-content-services/templates/config-infrastructure.yaml
Outdated
Show resolved
Hide resolved
helm/alfresco-content-services/templates/config-infrastructure.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK for me with Kibana disabled by default and a small doc on how to enable and secure it leveraging mechanisms provided by the bitnami chart
Co-authored-by: Alex Chapellon <alexandre.Chapellon@hyland.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should make it clear this is in case one uses the embedded elasticsearch which is not recommended for prod
--from-literal=AUDIT_ELASTICSEARCH_USERNAME=$ELASTIC_USERNAME \ | ||
--from-literal=AUDIT_ELASTICSEARCH_PASSWORD=$ELASTIC_PASSWORD \ | ||
--from-literal=SEARCH_USERNAME=$ELASTIC_USERNAME \ | ||
--from-literal=SEARCH_PASSWORD=$ELASTIC_PASSWORD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see --from-env-file
which should prevent user leaking credentials in its history
Ref: OPSEXP-2950