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.

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

Document how to set up remote clusters across k8s boundaries #2593

Merged
merged 23 commits into from
Feb 24, 2020

Conversation

pebrc
Copy link
Collaborator

@pebrc pebrc commented Feb 21, 2020

Add a page to our documentation outlining how to setup remote clusters if one of the clusters is residing in a different environment e.g. another k8s cluster.

@pebrc pebrc added the >docs Documentation label Feb 21, 2020
- protocol: TCP
port: 9300
targetPort: 9300
----
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be redundant once we have #2543

selector:
common.k8s.elastic.co/type: elasticsearch
elasticsearch.k8s.elastic.co/cluster-name: cluster_one
type: LoadBalancer
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will mostly work with cloud providers. I would add a note that it could also be done with an Ingress resource.

docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved
pebrc and others added 17 commits February 21, 2020 14:06
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Co-Authored-By: Charith Ellawala <52399125+charith-elastic@users.noreply.github.com>
Copy link
Contributor

@charith-elastic charith-elastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

kubectl create secret generic remote-certs --from-file=remote.ca.crt
----

Use this secret to configure `cluster_one`'s CA as a trusted CA in `cluster_two`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This assumes cluster_two is deployed through ECK, may be worth repeating again.

docs/remote-clusters.asciidoc Show resolved Hide resolved
docs/remote-clusters.asciidoc Outdated Show resolved Hide resolved

The link:https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-remote-clusters.html[remote clusters module] in Elasticsearch enables you to establish uni-directional connections to a remote cluster. This functionality is used in cross-cluster replication and cross-cluster search.

When using remote cluster connections with ECK, the necessary setup depends on where the remote cluster is deployed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When using remote cluster connections with ECK, the necessary setup depends on where the remote cluster is deployed.
When using remote cluster connections with ECK, the setup process depends on where the remote cluster is deployed.

@pebrc pebrc merged commit 6d710c3 into elastic:master Feb 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants