You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I need to run singlestoredb-dev-image in a Kubernetes Pod alongside other infrastructure (including MySQL) to run tests. I am attempting to upgrade from my customized CIAB image, in which I had overridden the startup script so that PORT could be set in the environment. This would cause the master node to use the specified port, and the leaf node to use PORT + 1.
I attempted a similar customization for the singlestoredb-dev-image. However, it appears that due to the execution of init.sh within the original image, I am unable to simply modify the file within my image to alter the ports.
Here is the script I use to populate the port argument in sdb-admin create-node and sdb-admin add-leaf:
Describe the solution you'd like
Add an environment variable to allow node port(s) to be customized and resolve port conflicts.
Describe alternatives you've considered
Writing my own Dockerfile, or figuring out an additional script to run to update the configurations or recreate the nodes (this is pretty unfavorable).
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I need to run singlestoredb-dev-image in a Kubernetes Pod alongside other infrastructure (including MySQL) to run tests. I am attempting to upgrade from my customized CIAB image, in which I had overridden the startup script so that
PORT
could be set in the environment. This would cause the master node to use the specified port, and the leaf node to usePORT + 1
.I attempted a similar customization for the singlestoredb-dev-image. However, it appears that due to the execution of
init.sh
within the original image, I am unable to simply modify the file within my image to alter the ports.Here is the script I use to populate the port argument in
sdb-admin create-node
andsdb-admin add-leaf
:Describe the solution you'd like
Add an environment variable to allow node port(s) to be customized and resolve port conflicts.
Describe alternatives you've considered
Writing my own Dockerfile, or figuring out an additional script to run to update the configurations or recreate the nodes (this is pretty unfavorable).
The text was updated successfully, but these errors were encountered: