Add Support for Unix Socket Connections in etcd Client #19760
Conversation
Improved etcd client usability by allowing connections to the server using the Unix socket format. Updated the validation logic to support Unix sockets for single-node setups while maintaining the requirement for 'host:port' URLs for multi-node clusters. This change addresses the limitation where Unix sockets were previously unsupported. Signed-off-by: borhanisaleh6 <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: SalehBorhani The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Hi @SalehBorhani. Thanks for your PR. I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
This pull request addresses #19704, which highlights the lack of support for connecting to etcd servers using the Unix socket format (unix://). The changes introduce support for Unix sockets, making it possible to leverage them in single-node etcd setups for local communication. The validation logic has been updated to allow Unix socket schemes while ensuring compatibility with the existing host:port format required for multi-node clusters.