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
[Feature] Opensearch Replication Plugin - Proxy mode connection setup #371
Comments
I have not tried setting up replication using kubernetes clusters. Other than the remote cluster setup you mentioned, you can also setup a connection using a proxy address which forwards to the OpenSearch cluster LB.
Let us know if this works for you. |
@soosinha I could not find remote connection creation using proxy mode in the documentation. |
We do have also this use-case when we need to perform CCR between 2 k8s clusters. Is there any limitation regarding using proxy mode? Couldn't find anything in the documentation. |
Currently, We don't have support for replication with |
Hi, Thanks, |
We are tracking v2.5.0 for this issue. |
I noticed that this feature is not marked as part of the 2.7.0 release on the opensearch roadmap. Is this because this CCR capability is being classified as a bug and not a feature? |
Hi, Thanks, |
@mrudrego we are finalizing the tasks under cross cluster replication for v2.7.0. |
@saikaranam-amazon, good to hear that and thanks for the response . |
Hi, Thanks, |
Hi @mrudrego, Can you try this configuration
|
Addressed here #786 |
Hello Opensearch community,
Is there a way to setup opensearch replication across 2 different kubernetes clusters?
Currently, the /_cluster/settings?pretty API accepts the following body:
{
"persistent": {
"cluster": {
"remote": {
"opensearch-cluster-alias": {
"seeds": ["0.0.0.0:9300"]
}
}
}
}
}
where “seeds” is the elastic discovery service name or IP address.
What I am trying to accomplish is use kubernetes ingress to route traffic to port 9300.
Any suggestions ?
Is replication plugin meant to be implemented across different kubernetes clusters ?
Thank you in advance,
Firdaus
The text was updated successfully, but these errors were encountered: