Skip to content
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.

Sign up for GitHub

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

Update doc #1319

Merged
merged 5 commits into from
Jul 22, 2019
Merged

Update doc #1319

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5072b08
Update persistent storage section
thbkrkr Jul 19, 2019
d45590a
Update kibana localhost url to use https
thbkrkr Jul 19, 2019
a04d042
Update k8s resources names in accessing-services doc
thbkrkr Jul 22, 2019
f009985
Mention SSL browser warning
thbkrkr Jul 22, 2019
21f67ae
Fix bulleted list
thbkrkr Jul 22, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/accessing-services.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ To access Elasticsearch, Kibana or APM Server, the operator manages a default us

[source,sh]
----
> kubectl get secret hulk-elastic-user -o go-template='{{.data.elastic | base64decode }}'
> kubectl get secret hulk-es-elastic-user -o go-template='{{.data.elastic | base64decode }}'
42xyz42citsale42xyz42
----

Expand Down Expand Up @@ -178,7 +178,7 @@ NAME=hulk
kubectl get secret "$NAME-ca" -o go-template='{{index .data "ca.pem" | base64decode }}' > ca.pem
PW=$(kubectl get secret "$NAME-elastic-user" -o go-template='{{.data.elastic | base64decode }}')

curl --cacert ca.pem -u elastic:$PW https://$NAME-es:9200/
curl --cacert ca.pem -u elastic:$PW https://$NAME-es-http:9200/
----

*Outside the Kubernetes cluster*
Expand All @@ -191,11 +191,11 @@ curl --cacert ca.pem -u elastic:$PW https://$NAME-es:9200/
----
NAME=hulk

kubectl get secret "$NAME-ca" -o go-template='{{index .data "ca.pem" | base64decode }}' > ca.pem
IP=$(kubectl get svc "$NAME-es" -o jsonpath='{.status.loadBalancer.ingress[].ip}')
PW=$(kubectl get secret "$NAME-elastic-user" -o go-template='{{.data.elastic | base64decode }}')
kubectl get secret "$NAME-es-http-certs-public" -o go-template='{{index .data "tls.crt" | base64decode }}' > tls.crt
IP=$(kubectl get svc "$NAME-es-http" -o jsonpath='{.status.loadBalancer.ingress[].ip}')
PW=$(kubectl get secret "$NAME-es-elastic-user" -o go-template='{{.data.elastic | base64decode }}')

curl --cacert ca.pem -u elastic:$PW https://$IP:9200/
curl --cacert tls.crt -u elastic:$PW https://$IP:9200/
----

Now you should get this message:
Expand Down
8 changes: 4 additions & 4 deletions docs/k8s-quickstart.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -230,7 +230,7 @@ Use `kubectl port-forward` to access Kibana from your local workstation:
kubectl port-forward service/quickstart-kb-http 5601
----
+
Open `http://localhost:5601` in your browser.
Open `https://localhost:5601` in your browser.
thbkrkr marked this conversation as resolved.
Show resolved Hide resolved
+
Login with the `elastic` user. Retrieve its password with:
+
Expand Down Expand Up @@ -267,11 +267,11 @@ EOF

[float]
[id="{p}-persistent-storage"]
=== Use persistent storage
=== Update persistent storage

Now that you have completed the quickstart, you can try out more features like using persistent storage. The cluster that you deployed in this quickstart uses a default persistent volume claim of 1GiB, without a storage class set. This means that the default storage class defined in the Kubernetes cluster is the one that will be provisioned.
Now that you have completed the quickstart, you can try out more features like tweaking persistent storage. The cluster that you deployed in this quickstart uses a default persistent volume claim of 1GiB, without a storage class set. This means that the default storage class defined in the Kubernetes cluster is the one that will be provisioned.

You can request a `PersistentVolumeClaim` in the cluster specification, to target any `PersistentVolume` class available in your Kubernetes cluster:
You can request a `PersistentVolumeClaim` with a larger size in the Elasticsearch specification or target any `PersistentVolume` class available in your Kubernetes cluster:

[source,yaml]
----
Expand Down