Once you have followed the steps in getting_started/installation.adoc for the operator and its dependencies, you will now go through the steps to set up and connect to an OpenSearch instance.
The configuration for the OpenSearch security plugin must be provided in a separate resource, e.g. a Secret:
link:example$getting_started/opensearch-security-config.yaml[role=include]Apply the Secret:
link:example$getting_started/getting_started.sh[role=include]The passwords in internal_users.yml are hashes using the bcrypt algorithm.
Such a hash can be e.g. generated with htpasswd:
$ htpasswd -nbBC 10 admin AJVFsGJBbpT6mChnq
admin:$2y$10$xRtHZFJ9QhG9GcYhRpAGpufCZYsk//nxsuel5URh0GWEBgmiI4Q/eOpenSearch nodes must be created as a custom resource; Create a file called opensearch.yaml:
link:example$getting_started/opensearch.yaml[role=include]And apply it:
link:example$getting_started/getting_started.sh[role=include]metadata.name contains the name of the OpenSearch cluster.
The previously created security plugin configuration must be referenced via podOverrides.
You need to wait for the OpenSearch nodes to finish deploying. You can do so with this command:
link:example$getting_started/getting_started.sh[role=include]Once the OpenSearch nodes are created, you can use the REST API of OpenSearch.
To forward the HTTP port (9200) to localhost, run:
link:example$getting_started/getting_started.sh[role=include]You can use the REST API as follows:
link:example$getting_started/getting_started.sh[role=include]Great! Now you can create your own indexes, populate them with data and search for it.
Check the usage-guide/index.adoc to find out more about configuring your OpenSearch instance or have a look at the OpenSearch documentation to ingest, search or visualize your data with OpenSearch Dashboards{external-link-icon}.