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

Issue with Redis Configuration in Kubernetes for Sysrepo Compilation #1664

Open
VishalGujela opened this issue Nov 11, 2024 · 1 comment
Open
Labels
is:enhancement Request for adding new feature or enahncing functionality.

Comments

@VishalGujela
Copy link

Hi,

I’ve been trying to set up Redis inside a Kubernetes cluster, but I'm facing an issue when compiling Sysrepo. As mentioned in the CMakeLists.txt of Sysrepo, the Redis configuration parameters need to be provided during the compilation:
**CMake

Redis username, password, host, and port for the client

set(REDIS_USERNAME "" CACHE STRING "Username for Redis user, all operations are done via this client in case Redis plugin is supported. If not provided, no authentication is done.")
set(REDIS_PASSWORD "" CACHE STRING "Password for Redis user in case Redis plugin is supported.")
set(REDIS_HOST "192.167.67.100" CACHE STRING "Host for the Redis client to connect to.")
set(REDIS_PORT 6379 CACHE STRING "Port for the Redis client to connect to.")**
However, since Redis is running inside Kubernetes with a dynamically assigned IP, I’m unable to ping the specified IP address (192.167.67.100) during the compilation process.

How should I proceed with the compilation if Redis is not reachable by this static IP? Is there an alternative way to configure Sysrepo when Redis is running inside a Kubernetes environment with dynamic IPs?

Thanks,
Vishal

@michalvasko
Copy link
Member

The plugin was implemented generally assuming it will be used locally but it can also connect to a specific IP address. Your use-case is not supported currently. You can provide a patch if you want but I do not think there is a simple way to support this. An environment variable would work but seems like an unsafe way for communicating this kind of information.

@michalvasko michalvasko added the is:enhancement Request for adding new feature or enahncing functionality. label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:enhancement Request for adding new feature or enahncing functionality.
Projects
None yet
Development

No branches or pull requests

2 participants