[CORENET-2649] Add sock proxy to cluster-network-operator so egressip can use grpc to reach worker nodes - Red Hat Issue Tracker

Type: Story
Resolution: Done
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: OVN Kubernetes
Labels:
- migrated-from-sdn

Story Points:
3
Blocked:
False
Blocked Reason:
None
Ready:
False
Epic Link:
Egress IP refactor
BZ Doc Type:
If docs needed, set a value
BZ requires_doc_text:
Unset
Dev Approval:
?
Docs Approval:
?
PM Approval:
?
QE Approval:
?
Solution:
Untriaged
Support Scope:
Not Supported
[QE] How to address?:
---
BZ Keywords:
- Unset

Sprint:
SDN Sprint 224, SDN Sprint 225
WSJF:
0

Root Cause:
Untriaged

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

Add sock proxy to cluster-network-operator so egressip can use grpc to reach worker nodes.

With the introduction of grpc as means for determining the state of a given egress node, hypershift should
be able to leverage socks proxy and become able to know the state of each egress node.

References relevant to this work:
1281-network-proxy
[+https://coreos.slack.com/archives/C01C8502FMM/p1658427627751939+]
[+https://github.com/openshift/hypershift/pull/1131/commits/28546dc587dc028dc8bded715847346ff99d65ea+]

links to

openshift/cluster-network-operator#1539: SDN-3283: HyperShift: Use a socks-proxy in ovnkube-master to allow for node heath checks

openshift/hypershift#1731: SDN-3283: CNO: Add an environment variable with socks5-proxy image

Use a custom dialer for GRPC to allow connectivity over a socks proxy

Assignee:: Patryk Diak

Reporter:: Flavio Fernandes (Inactive)

Contributors:: Patryk Diak

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2022/07/22 8:04 PM

Updated:: 2025/03/30 8:13 PM

Resolved:: 2022/09/22 7:35 PM