spidernet-io / egressgateway

Network egress policy for Kubernetes

Home Page:https://spidernet-io.github.io/egressgateway/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

When first create egressgateway CR,the status of IPV4/IPV6 TOTAL or IPV4/IPV6 FREE is emtpy

bzsuni opened this issue · comments

The egressgateway yaml

apiVersion: egressgateway.spidernet.io/v1beta1
kind: EgressGateway
metadata:
  name: egw-test
spec:
  ippools:
    ipv4:
    - 172.18.1.2-172.18.4.33
    ipv6:
    - fd18::2-fd18::321
  nodeSelector:
    selector:
      matchLabels:
        egress: "yes"

After create it

 kubectl get egw egw-test -oyaml

apiVersion: egressgateway.spidernet.io/v1beta1
kind: EgressGateway
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"egressgateway.spidernet.io/v1beta1","kind":"EgressGateway","metadata":{"annotations":{},"name":"egw-test"},"spec":{"ippools":{"ipv4":["172.18.1.2-172.18.4.33"],"ipv6":["fd18::2-fd18::321"]},"nodeSelector":{"selector":{"matchLabels":{"egress":"yes"}}}}}
  creationTimestamp: "2024-03-06T06:29:49Z"
  finalizers:
  - egressgateway.spidernet.io/egressgateway
  generation: 1
  name: egw-test
  resourceVersion: "51377"
  uid: da828623-23f6-4ea3-afee-200cda100197
spec:
  ippools:
    ipv4:
    - 172.18.1.2-172.18.4.33
    ipv4DefaultEIP: 172.18.3.138
    ipv6:
    - fd18::2-fd18::321
    ipv6DefaultEIP: fd18::122
  nodeSelector:
    selector:
      matchLabels:
        egress: "yes"

The status is not update

The gateway at least match one node as the gateway-node