Closed manuelbuil closed 10 months ago
Results from the dualstack test run
E2E_NODE_ROLES="server-0 agent-0" E2E_NODE_BOXES="generic/ubuntu2004 generic/ubuntu2004" vagrant up server-0 &> vagrant.log
CLUSTER CONFIG
OS: generic/ubuntu2004
Server Nodes: [server-0]
Agent Nodes: [agent-0]
{"state":"passed","name":"Starts up with no issues","type":"k3s test","time":214401249093}•agent-0 Ready <none> 9s v1.27.8+k3s-9edb565d 10.10.10.101 10.10.10.101 Ubuntu 20.04.6 LTS 5.4.0-163-generic containerd://1.7.11-k3s2.27
server-0 Ready control-plane,etcd,master 109s v1.27.8+k3s-9edb565d 10.10.10.100 10.10.10.100 Ubuntu 20.04.6 LTS 5.4.0-163-generic containerd://1.7.11-k3s2.27
{"state":"passed","name":"Checks Node Status","type":"k3s test","time":185289084}•kube-system coredns-77ccd57875-drssd 1/1 Running 0 94s 10.42.0.6 server-0 <none> <none>
kube-system helm-install-traefik-crd-s652t 0/1 Completed 0 94s 10.42.0.4 server-0 <none> <none>
kube-system helm-install-traefik-rzlwg 0/1 Completed 2 94s 10.42.0.2 server-0 <none> <none>
kube-system local-path-provisioner-957fdf8bc-5rffz 1/1 Running 0 94s 10.42.0.3 server-0 <none> <none>
kube-system metrics-server-648b5df564-bgc2j 1/1 Running 0 94s 10.42.0.5 server-0 <none> <none>
kube-system svclb-traefik-bf412e29-9lnl6 2/2 Running 0 9s 10.42.1.2 agent-0 <none> <none>
kube-system svclb-traefik-bf412e29-rjl6h 2/2 Running 0 57s 10.42.0.7 server-0 <none> <none>
kube-system traefik-768bdcdcdd-tswbl 1/1 Running 0 57s 10.42.0.8 server-0 <none> <none>
{"state":"passed","name":"Checks Pod Status","type":"k3s test","time":176457556}•{"state":"passed","name":"Verifies that each node has IPv4 and IPv6","type":"k3s test","time":84366382}•{"state":"passed","name":"Verifies that each pod has IPv4 and IPv6","type":"k3s test","time":96671821}•
Deploying dualstack_clusterip.yaml
{"state":"passed","name":"Verifies ClusterIP Service","type":"k3s test","time":30507144989}•
Deploying dualstack_ingress.yaml
{"state":"passed","name":"Verifies Ingress","type":"k3s test","time":566472291}•
Deploying dualstack_nodeport.yaml
{"state":"passed","name":"Verifies NodePort Service","type":"k3s test","time":2665074577}•
Deploying pod_client.yaml
Deploying netpol-fail.yaml
Deploying netpol-work.yaml
{"state":"passed","name":"Verifies podSelector Network Policy","type":"k3s test","time":5821589550}•
Ran 9 of 9 Specs in 263.009 seconds
SUCCESS! -- 9 Passed | 0 Failed | 0 Pending | 0 Skipped
Pods and svcs have different address range
vagrant@server-0:~$ k3s -v
k3s version v1.27.8+k3s-9edb565d (9edb565d)
go version go1.20.11
vagrant@server-0:~$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
agent-0 Ready <none> 30s v1.27.8+k3s-9edb565d
server-0 Ready control-plane,etcd,master 2m10s v1.27.8+k3s-9edb565d
vagrant@server-0:~$ kubectl get pods -A -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
default ds-clusterip-pod-f4b45cd86-4qsg4 1/1 Running 0 26s 10.42.1.3 agent-0 <none> <none>
default ds-clusterip-pod-f4b45cd86-6qgms 1/1 Running 0 26s 10.42.0.9 server-0 <none> <none>
kube-system coredns-77ccd57875-drssd 1/1 Running 0 2m1s 10.42.0.6 server-0 <none> <none>
kube-system helm-install-traefik-crd-s652t 0/1 Completed 0 2m1s 10.42.0.4 server-0 <none> <none>
kube-system helm-install-traefik-rzlwg 0/1 Completed 2 2m1s 10.42.0.2 server-0 <none> <none>
kube-system local-path-provisioner-957fdf8bc-5rffz 1/1 Running 0 2m1s 10.42.0.3 server-0 <none> <none>
kube-system metrics-server-648b5df564-bgc2j 1/1 Running 0 2m1s 10.42.0.5 server-0 <none> <none>
kube-system svclb-traefik-bf412e29-9lnl6 2/2 Running 0 36s 10.42.1.2 agent-0 <none> <none>
kube-system svclb-traefik-bf412e29-rjl6h 2/2 Running 0 84s 10.42.0.7 server-0 <none> <none>
kube-system traefik-768bdcdcdd-tswbl 1/1 Running 0 84s 10.42.0.8 server-0 <none> <none>
vagrant@server-0:~$ kubectl get svc -A
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default ds-clusterip-svc ClusterIP 10.43.113.87 <none> 80/TCP 32s
default ds-nodeport-svc NodePort 10.43.58.127 <none> 80:30096/TCP 1s
default kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 2m22s
kube-system kube-dns ClusterIP 10.43.0.10 <none> 53/UDP,53/TCP,9153/TCP 2m18s
kube-system metrics-server ClusterIP 10.43.20.110 <none> 443/TCP 2m17s
kube-system traefik LoadBalancer 10.43.108.149 10.10.10.100,10.10.10.101,fd11:decf:c0ff:ee::10,fd11:decf:c0ff:ee::11 80:32246/TCP,443:30911/TCP 91s
Backport: https://github.com/k3s-io/k3s/issues/8911