spidernet-io / egressgateway Goto Github PK

Describe the version
egressgateway v0.1.0

Describe the bug
after changing the mac address of egress.vxlan on the node, the mac address did not restore its original value based on the egressnode cr status.tunnelMac

Hwo To Reproduce
Steps to reproduce the issue:

1. check egressnode cr egressgateway-worker status.tunnelMac
   
2. change the egress.vxlan mac address
   
3. the mac address did not restore its original value based on the egressnode cr status.tunnelMac

Expected behavior
the mac address should restore its original value based on the egressnode cr status.tunnelMac

Describe the version

Describe the bug

Consider a pod(located in node A) backing a LoadBalancer service, and the pod is matched an egress rule: the packets of pod access to external forwarded via Node B.

Now I announced the loadBalancer IP to node A via metallb L2 mode. In this case, the LB IP cannot be accessed by clients outside the cluster.

• External client: 1.1.1.1
• LoadBalancer(announced in nodeA): 10.6.212.100
• Backend Pod IP(in nodeA): 10.244.0.1
• EgressGateway: Node B
• Node A IP: 10.6.212.101
• Node B IP: 10.6.212.102

package flow:

request package: 1.1.1.1(client) -> 10.6.212.100(lb IP) -> Node A -> dnat -> 10.244.0.1
reply package: 10.244.0.1 -> match egressRule -> Node B -> ?（drop）

Hwo To Reproduce
Steps to reproduce the issue:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots and log
If applicable, add screenshots and log to help explain your problem.

Additional context
Add any other context about the problem here.

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3434616678

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3688894799

Documentation issue

1. miss documentation
2. documentation go wrong

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3434592565

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3714463497

action url: https://github.com/spidernet-io/egressgateway/actions/runs/4725287802

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3434566680

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3698288517

Work in default calico config.

In most use cases the chainInsertMode is set to the default value.
Would we improve the egress gateway to support calico chainInsertMode=Insert

Describe the version
egressgateway v0.1.0

Describe the bug
the status.physicalInterface of the egressnode cr have not been upgrade after i changed the node interface name

Hwo To Reproduce
Steps to reproduce the issue:

1. change the interface name of one one of your cluster
2. check the status.physicalInterface of the egressnode cr on the node

Expected behavior
we expect that the status.physicalInterface of the egressnode cr would be upgraded same with the node interface name

Screenshots and log

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3721560159

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3434536496

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3526672154

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3434584456

• Support make update_chart_version on macOS
• Update the image tag of values at the same time

refer to: #217

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3716141106

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3707500975

1 verify datapath model with calico cilium macvlan

2 update datapath designe markdown

3 tcp udp websocket

action url: https://github.com/spidernet-io/egressgateway/actions/runs/4568473907

action url: https://github.com/spidernet-io/egressgateway/actions/runs/4226691602

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3726360187

When EgressGateway creation preceded node labeling, EgressGateway CR status not updated.

Bug reported by @bzsuni.

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3434567761

Describe the version

0.1.0 rc1

Describe the bug
A clear and concise description of what the bug is.

{
    "msg":"Reconciler error%!(EXTRA []interface {}=[])",
    "error":"EgressGateway.egressgateway.spidernet.io "default" is invalid: status.nodeList.interfaceStatus: Invalid value: "null": status.nodeList.interfaceStatus in body must be of type array: "null"
}

action url: https://github.com/spidernet-io/egressgateway/actions/runs/4441130397

Fix in #179

the egress need rp_filter=0

it could refer to cilium code
https://github.com/cilium/cilium/blob/master/tools/sysctlfix/main.go#L39

Describe the version

Describe the bug
A clear and concise description of what the bug is.

workstation:~$ ip r show table 50
default
	nexthop via 192.200.168.78 dev egress.vxlan weight 1
	nexthop via 192.200.230.246 dev egress.vxlan weight 1
workstation:~$ ip r show table 50
default via 192.200.168.78 dev egress.vxlan

Hwo To Reproduce
Steps to reproduce the issue:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots and log
If applicable, add screenshots and log to help explain your problem.

Additional context
Add any other context about the problem here.

action url: https://github.com/spidernet-io/egressgateway/actions/runs/4409015198

(1) 优化1 , server

（2） 优化2 , client
client ，可以是 支持 压测 用法，输入 命令行参数 “目标地址（v4 v6）” “tps” “压测时间” “每个请求的超时时间定义” 等等，
最终输出 成功率 等等输出
后续 E2E 压测等，皆可 复用该 程序

customize the snat of egress source ip

action url: https://github.com/spidernet-io/egressgateway/actions/runs/3434636330

Describe the version
v0.1.0

Describe the bug

root@dual-worker2:/#
root@dual-worker2:/# iptables -t nat -nvL POSTROUTING
Chain POSTROUTING (policy ACCEPT 6450 packets, 389K bytes)
 pkts bytes target     prot opt in     out     source               destination
 6461  389K KUBE-POSTROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* kubernetes postrouting rules */
    0     0 DOCKER_POSTROUTING  all  --  *      *       0.0.0.0/0            172.18.0.1
 6294  379K FLANNEL-POSTRTG  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* flanneld masq */

# After the agent is restarted, the ACCEPT rule is restored. This problem may also exist in other ACCEPT rules

root@dual-worker2:/# iptables -t nat -nvL POSTROUTING
Chain POSTROUTING (policy ACCEPT 6484 packets, 391K bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* egw:OucywG_GSKckREz8 */ mark match 0x12000000
 6496  392K KUBE-POSTROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* kubernetes postrouting rules */
    0     0 DOCKER_POSTROUTING  all  --  *      *       0.0.0.0/0            172.18.0.1
 6328  381K FLANNEL-POSTRTG  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* flanneld masq */
root@dual-worker2:/#