-
Notifications
You must be signed in to change notification settings - Fork 277
K8s: OSS Cluster API limitation #1670
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
Conversation
andy-stark-redis
left a comment
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.
Tiny issue, otherwise LGTM.
Co-authored-by: andy-stark-redis <[email protected]>
heinrich-redislabs
left a comment
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.
Approved with a small improvement suggestion.
|
|
||
| ## OSS Cluster API limitations | ||
|
|
||
| When using [OSS Cluster API]({{< relref "/operate/rs/databases/configure/oss-cluster-api" >}}) with Redis Enterprise for Kubernetes, clients must specify the IP addresses of Redis instances to perform operations. Since Pod IP addresses are internal to the Kubernetes cluster and not publicly accessible, **OSS Cluster API can only be used by clients running on pods within the same Kubernetes cluster as the Redis Enterprise pods.** Using OSS Cluster API from outside the Kubernetes cluster is not tested and currently not supported. |
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.
The with Redis Enterprise for Kubernetes is not really necessary, because the limitation holds for k8s/non-k8s deployments.
DOC-5101