File tree Expand file tree Collapse file tree 2 files changed +34
-7
lines changed
kubernetes/samples/scripts/elasticsearch-and-kibana Expand file tree Collapse file tree 2 files changed +34
-7
lines changed Original file line number Diff line number Diff line change 1- ** TODO** write me
1+ # Sample to deploy Elasticsearch and Kibana
2+
3+
4+ When a user installs the WebLogic operator Helm chart, the user can set
5+ ` elkIntegrationEnabled ` to ` true ` in their ` values.yaml ` to tell the operator to send the
6+ contents of the operator's logs to Elasticsearch.
7+
8+ Typically, a user would have already configured Elasticsearch and Kibana in the
9+ Kubernetes cluster, and also would specify ` elasticSearchHost ` and ` elasticSearchPort `
10+ in their ` values.yaml ` file to point to where Elasticsearch is already running.
11+
12+ This sample configures the Elasticsearch and Kibana deployments and services.
13+ It's useful for trying out the operator in a Kubernetes cluster that doesn't already
14+ have them configured.
15+
16+ It runs Elasticstack on the same host and port that the operator's Helm chart defaults
17+ to, therefore, the customer only needs to set elkIntegrationEnabled to true in their
18+ ` values.yaml ` file.
19+
20+ To install ElasticSearch and Kibana, use:
21+ ```
22+ kubectl apply -f kubernetes/samples/scripts/elasticsearch_and_kibana.yaml
23+ ```
24+
25+ To remove them, use:
26+ ```
27+ kubectl apply -f kubernetes/samples/scripts/elasticsearch_and_kibana.yaml
28+ ```
Original file line number Diff line number Diff line change 11# Copyright 2018 Oracle Corporation and/or its affiliates. All rights reserved.
22# Licensed under the Universal Permissive License v 1.0 as shown at http://oss.oracle.com/licenses/upl.
33
4- # When the customer installs the weblogic operator helm chart, the customer can set
4+ # When a user installs the WebLogic operator Helm chart, the user can set
55# elkIntegrationEnabled to true in their values.yaml to tell the operator to send the
6- # contents of the operator's log to elasticsearch .
6+ # contents of the operator's log to Elasticsearch .
77#
8- # Typically, a customer would have already configured elasticsearch and kibana in the
8+ # Typically, a user would have already configured Elasticsearch and Kibana in the
99# Kubernetes cluster, and also would specify elasticSearchHost and elasticSearchPort
10- # in their values.yaml file to point to where elasticsearch is already running.
10+ # in their values.yaml file to point to where Elasticsearch is already running.
1111#
12- # This sample configures the elasticsearch and kibana deployments and services.
12+ # This sample configures the Elasticsearch and Kibana deployments and services.
1313# It's useful for trying out the operator in a Kubernetes cluster that doesn't already
1414# have them configured.
1515#
16- # It runs elasticstack on the same host and port that the operator's helm chart defaults
16+ # It runs Elasticstack on the same host and port that the operator's Helm chart defaults
1717# to, therefore, the customer only needs to set elkIntegrationEnabled to true in their
1818# values.yaml file.
1919#
You can’t perform that action at this time.
0 commit comments