可以看到 除了 kube-von 自己的服务，其他的依旧只有 ipv4 的 lb， 应该是这些服务还有别的什么地方需要配置，才能使用双栈。
(.venv) root@empty:~# kgp
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system coredns-5d78c9869d-fjqvj 1/1 Running 0 10m 10.16.0.7 kube-ovn-control-plane <none> <none>
kube-system coredns-5d78c9869d-lnnjm 1/1 Running 0 10m 10.16.0.6 kube-ovn-worker <none> <none>
kube-system etcd-kube-ovn-control-plane 1/1 Running 0 11m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system kube-apiserver-kube-ovn-control-plane 1/1 Running 0 11m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system kube-controller-manager-kube-ovn-control-plane 1/1 Running 0 11m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system kube-ovn-cni-bf4dh 1/1 Running 0 10m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system kube-ovn-cni-tsf42 1/1 Running 0 10m 172.18.0.3 kube-ovn-worker <none> <none>
kube-system kube-ovn-controller-658898f586-wlnmv 1/1 Running 0 10m 172.18.0.3 kube-ovn-worker <none> <none>
kube-system kube-ovn-monitor-b57b8b96b-8t6tj 1/1 Running 0 10m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system kube-ovn-pinger-7756z 1/1 Running 0 10m 10.16.0.8 kube-ovn-control-plane <none> <none>
kube-system kube-ovn-pinger-x4lk9 1/1 Running 0 10m 10.16.0.9 kube-ovn-worker <none> <none>
kube-system kube-proxy-fjk72 1/1 Running 0 10m 172.18.0.3 kube-ovn-worker <none> <none>
kube-system kube-proxy-t4tjs 1/1 Running 0 10m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system kube-scheduler-kube-ovn-control-plane 1/1 Running 0 11m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system ovn-central-7bb79c5c57-vnb9z 1/1 Running 0 10m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system ovs-ovn-64t5x 1/1 Running 0 10m 172.18.0.2 kube-ovn-control-plane <none> <none>
kube-system ovs-ovn-rdlv6 1/1 Running 0 10m 172.18.0.3 kube-ovn-worker <none> <none>
slr-3040 client-20769 1/1 Running 0 20s 10.242.87.2 kube-ovn-worker <none> <none>
slr-3040 sts-20769-0 1/1 Running 0 16s 10.242.87.3 kube-ovn-worker <none> <none>
slr-6971 client-79590 0/1 Terminating 0 9m34s <none> kube-ovn-worker <none> <none>
(.venv) root@empty:~#
(.venv) root@empty:~#
(.venv) root@empty:~#
(.venv) root@empty:~#
(.venv) root@empty:~#
(.venv) root@empty:~# k get svc -A -o wide
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
default kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 11m <none>
kube-system kube-dns ClusterIP 10.96.0.10 <none> 53/UDP,53/TCP,9153/TCP 11m k8s-app=kube-dns
kube-system kube-ovn-cni ClusterIP 10.97.205.241 <none> 10665/TCP 10m app=kube-ovn-cni
kube-system kube-ovn-controller ClusterIP 10.104.212.173 <none> 10660/TCP 10m app=kube-ovn-controller
kube-system kube-ovn-monitor ClusterIP 10.98.71.7 <none> 10661/TCP 10m app=kube-ovn-monitor
kube-system kube-ovn-pinger ClusterIP 10.106.188.243 <none> 8080/TCP 10m app=kube-ovn-pinger
kube-system ovn-nb ClusterIP 10.111.41.9 <none> 6641/TCP 10m app=ovn-central,ovn-nb-leader=true
kube-system ovn-northd ClusterIP 10.103.84.99 <none> 6643/TCP 10m app=ovn-central,ovn-northd-leader=true
kube-system ovn-sb ClusterIP 10.111.22.12 <none> 6642/TCP 10m app=ovn-central,ovn-sb-leader=true
slr-3040 sts-20769 ClusterIP 10.102.245.71 <none> 8090/TCP 27s app=slr
(.venv) root@empty:~# k get svc -n slr-3040 sts-20769 -o yaml
apiVersion: v1
kind: Service
metadata:
annotations:
ovn.kubernetes.io/logical_switch: subnet-20769
ovn.kubernetes.io/vpc: vpc-20769
creationTimestamp: "2023-07-18T01:23:49Z"
name: sts-20769
namespace: slr-3040
resourceVersion: "2211"
uid: 01526ebd-9de9-48b8-931e-6dc65dbf2065
spec:
clusterIP: 10.102.245.71
clusterIPs:
- 10.102.245.71
- fd00:10:96::a39f
internalTrafficPolicy: Cluster
ipFamilies:
- IPv4
- IPv6
ipFamilyPolicy: PreferDualStack
ports:
- name: netcat
port: 8090
protocol: TCP
targetPort: 80
selector:
app: slr
sessionAffinity: None
type: ClusterIP
status:
loadBalancer: {}
(.venv) root@empty:~# k ko nbctl lb-list
UUID LB PROTO VIP IPs
b97b8419-c721-485c-8b03-59270fa825c5 cluster-tcp-load tcp 10.103.84.99:6643 172.18.0.2:6643
tcp 10.104.212.173:10660 172.18.0.3:10660
tcp 10.106.188.243:8080 10.16.0.8:8080,10.16.0.9:8080
tcp 10.111.22.12:6642 172.18.0.2:6642
tcp 10.111.41.9:6641 172.18.0.2:6641
tcp 10.96.0.10:53 10.16.0.6:53,10.16.0.7:53
tcp 10.96.0.10:9153 10.16.0.6:9153,10.16.0.7:9153
tcp 10.96.0.1:443 172.18.0.2:6443
tcp 10.97.205.241:10665 172.18.0.2:10665,172.18.0.3:10665
tcp 10.98.71.7:10661 172.18.0.2:10661
tcp [fd00:10:96::178]:10665 [fc00:f853:ccd:e793::2]:10665,[fc00:f853:ccd:e793::3]:10665
tcp [fd00:10:96::2e8c]:6641 [fc00:f853:ccd:e793::2]:6641
tcp [fd00:10:96::397a]:8080 [fd00:10:16::8]:8080,[fd00:10:16::9]:8080
tcp [fd00:10:96::7a78]:6642 [fc00:f853:ccd:e793::2]:6642
tcp [fd00:10:96::96ef]:10661 [fc00:f853:ccd:e793::2]:10661
tcp [fd00:10:96::bc2d]:6643 [fc00:f853:ccd:e793::2]:6643
tcp [fd00:10:96::d26d]:10660 [fc00:f853:ccd:e793::3]:10660
740ce153-1c1f-4312-a914-e003567056cf cluster-udp-load udp 10.96.0.10:53 10.16.0.6:53,10.16.0.7:53
8c8dd9f4-4254-4f94-92fe-6a17c8388224 vpc-vpc-20769-tc tcp 10.102.245.71:8090 10.242.87.3:80
tcp [fd00:10:96::a39f]:8090 [fc00:10:ff:0:2:7da0:0:3]:80
(.venv) root@empty:~#
