We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
An issue in Spring Cloud Connectors gives examples of two service brokers that provide sentinel connection details in service binding credentials.
The text was updated successfully, but these errors were encountered:
Tanzu for Valkey now supports sentinels
The credentials format is like below: https://docs.vmware.com/en/VMware-Tanzu-for-Valkey-on-Cloud-Foundry/4.0/valkey-tanzu-cloud-foundry/appdevs.html#check-availability-6
# schema for non-ha service-instances { "host": "q-s0.redis-instance.ENVIRONMENT-NAME-services-subnet.service-instance-GUID.bosh", "password": YOUR-PASSWORD, "port": INSECURE-PORT-NUMBER, "tls_port": SECURE-PORT-NUMBER } # schema for ha service-instances { "master_name": "redis-master", "password": YOUR-REDIS-PASSWORD, "port": INSECURE-REDIS-PORT-NUMBER, "sentinel_password": YOUR-SENTINEL-PASSWORD, "sentinels": [ {"host": INSTANCE-1-HOSTNAME, "port": INSECURE-SENTINEL-PORT-NUMBER, "tls_port": SECURE-SENTINEL-PORT-NUMBER}, {"host": INSTANCE-2-HOSTNAME, "port": INSECURE-SENTINEL-PORT-NUMBER, "tls_port": SECURE-SENTINEL-PORT-NUMBER}, {"host": INSTANCE-3-HOSTNAME, "port": INSECURE-SENTINEL-PORT-NUMBER, "tls_port": SECURE-SENTINEL-PORT-NUMBER}, ], "tls_port": SECURE-REDIS-PORT-NUMBER, "tls_versions": SUPPORTED_TLS_VERSIONS }
Can you please support this format for sentinels?
Sorry, something went wrong.
No branches or pull requests
An issue in Spring Cloud Connectors gives examples of two service brokers that provide sentinel connection details in service binding credentials.
The text was updated successfully, but these errors were encountered: