rancher-partner-charts/charts/elastic/elasticsearch/examples/security
Samuel Attwood 5335667721 Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
..
test Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
Makefile Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
README.md Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00
values.yaml Removing unpacked chart versions. Changing configuration to just store latest release to reduce quantity of tracked files over time 2022-12-01 23:19:00 -05:00

README.md

Security

This example deploy a 3 nodes Elasticsearch 8.5.1 with authentication and autogenerated certificates for TLS (see values).

Note that this configuration should be used for test only. For a production deployment you should generate SSL certificates following the official docs.

Usage

  • Create the required secrets: make secrets

  • Deploy Elasticsearch chart with the default values: make install

  • You can now setup a port forward to query Elasticsearch API:

    kubectl port-forward svc/security-master 9200
    curl -u elastic:changeme https://localhost:9200/_cat/indices
    

Testing

You can also run goss integration tests using make test