-
Notifications
You must be signed in to change notification settings - Fork 718
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
Conversation
- protocol: TCP | ||
port: 9300 | ||
targetPort: 9300 | ||
---- |
There was a problem hiding this comment.
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
docs/remote-clusters.asciidoc
Outdated
selector: | ||
common.k8s.elastic.co/type: elasticsearch | ||
elasticsearch.k8s.elastic.co/cluster-name: cluster_one | ||
type: LoadBalancer |
There was a problem hiding this comment.
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.
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>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
docs/remote-clusters.asciidoc
Outdated
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`: |
There was a problem hiding this comment.
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
Outdated
|
||
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
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.