9a719e2a18
This change enables TLS between Elasticsearch and Kibana data path. Note that TLS terminates at apache-proxy container of the Elasticsearch-client pod, not directly to port 9200 of elasticsearch-client container. Since all data traffic goes through apache-proxy container, fluentd output to Elasticsearch are configured to have TLS enabled as well. In additon, other Elasticsearch pods that communicate with Elasticsearch-client endpoint are modified to provide the cacert option with curl. Change-Id: I3373c0c350b30c175be4a34d25a403b9caf74294 |
||
---|---|---|
.. | ||
bin | ||
monitoring/prometheus | ||
certificates.yaml | ||
configmap-bin-curator.yaml | ||
configmap-bin-elasticsearch.yaml | ||
configmap-etc-curator.yaml | ||
configmap-etc-elasticsearch.yaml | ||
cron-job-curator.yaml | ||
cron-job-verify-repositories.yaml | ||
deployment-client.yaml | ||
deployment-gateway.yaml | ||
ingress-elasticsearch.yaml | ||
job-elasticsearch-template.yaml | ||
job-image-repo-sync.yaml | ||
job-s3-bucket.yaml | ||
job-s3-user.yaml | ||
network-policy.yaml | ||
pod-helm-tests.yaml | ||
secret-elasticsearch.yaml | ||
secret-environment.yaml | ||
secret-ingress-tls.yaml | ||
secret-s3-user.yaml | ||
service-data.yaml | ||
service-discovery.yaml | ||
service-gateway.yaml | ||
service-ingress-elasticsearch.yaml | ||
service-logging.yaml | ||
statefulset-data.yaml | ||
statefulset-master.yaml |