ShylajaDevadiga
commented
10 months ago Validated using latest commit id 57a942cee0ff7df91f553e24299c2c0d686c0319 on release-1.26
Results from dualstack test:
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":223273526886}•agent-0 Ready <none> 8s v1.26.11+k3s-57a942ce 10.10.10.101 10.10.10.101 Ubuntu 20.04.6 LTS 5.4.0-163-generic containerd://1.7.11-k3s2.26
server-0 Ready control-plane,etcd,master 109s v1.26.11+k3s-57a942ce 10.10.10.100 10.10.10.100 Ubuntu 20.04.6 LTS 5.4.0-163-generic containerd://1.7.11-k3s2.26
{"state":"passed","name":"Checks Node Status","type":"k3s test","time":169833927}•kube-system coredns-59b4f5bbd5-ggrrd 1/1 Running 0 100s 10.42.0.6 server-0 <none> <none>
kube-system helm-install-traefik-7smk8 0/1 Completed 2 101s 10.42.0.2 server-0 <none> <none>
kube-system helm-install-traefik-crd-5zdvp 0/1 Completed 0 101s 10.42.0.4 server-0 <none> <none>
kube-system local-path-provisioner-76d776f6f9-ksl5j 1/1 Running 0 100s 10.42.0.3 server-0 <none> <none>
kube-system metrics-server-68cf49699b-qlsjf 1/1 Running 0 100s 10.42.0.5 server-0 <none> <none>
kube-system svclb-traefik-bc65a13c-qflp9 2/2 Running 0 13s 10.42.1.2 agent-0 <none> <none>
kube-system svclb-traefik-bc65a13c-v9w66 2/2 Running 0 60s 10.42.0.7 server-0 <none> <none>
kube-system traefik-dd49d7bb6-75c97 1/1 Running 0 60s 10.42.0.8 server-0 <none> <none>
{"state":"passed","name":"Checks Pod Status","type":"k3s test","time":5263189139}•{"state":"passed","name":"Verifies that each node has IPv4 and IPv6","type":"k3s test","time":78851837}•{"state":"passed","name":"Verifies that each pod has IPv4 and IPv6","type":"k3s test","time":100111154}•
Deploying dualstack_clusterip.yaml
{"state":"passed","name":"Verifies ClusterIP Service","type":"k3s test","time":25330517336}•
Deploying dualstack_ingress.yaml
{"state":"passed","name":"Verifies Ingress","type":"k3s test","time":2534023676}•
Deploying dualstack_nodeport.yaml
{"state":"passed","name":"Verifies NodePort Service","type":"k3s test","time":2699689639}•
Deploying pod_client.yaml
Deploying netpol-fail.yaml
Deploying netpol-work.yaml
{"state":"passed","name":"Verifies podSelector Network Policy","type":"k3s test","time":4701776812}•
Ran 9 of 9 Specs in 272.252 seconds
SUCCESS! -- 9 Passed | 0 Failed | 0 Pending | 0 SkippedPods and svcs from different address range
vagrant@server-0:~$ k3s -v
k3s version v1.26.11+k3s-57a942ce (57a942ce)
go version go1.20.11
vagrant@server-0:~$ kubectl get pods -o wide -A
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system coredns-59b4f5bbd5-ggrrd 1/1 Running 0 57s 10.42.0.6 server-0 <none> <none>
kube-system helm-install-traefik-7smk8 0/1 Completed 2 58s 10.42.0.2 server-0 <none> <none>
kube-system helm-install-traefik-crd-5zdvp 0/1 Completed 0 58s 10.42.0.4 server-0 <none> <none>
kube-system local-path-provisioner-76d776f6f9-ksl5j 1/1 Running 0 57s 10.42.0.3 server-0 <none> <none>
kube-system metrics-server-68cf49699b-qlsjf 1/1 Running 0 57s 10.42.0.5 server-0 <none> <none>
kube-system svclb-traefik-bc65a13c-v9w66 2/2 Running 0 17s 10.42.0.7 server-0 <none> <none>
kube-system traefik-dd49d7bb6-75c97 1/1 Running 0 17s 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 kubernetes ClusterIP 10.43.0.1 <none> 443/TCP 77s
kube-system kube-dns ClusterIP 10.43.0.10 <none> 53/UDP,53/TCP,9153/TCP 73s
kube-system metrics-server ClusterIP 10.43.154.216 <none> 443/TCP 71s
kube-system traefik LoadBalancer 10.43.234.232 10.10.10.100,fd11:decf:c0ff:ee::10 80:31824/TCP,443:31673/TCP 21s
Backport: https://github.com/k3s-io/k3s/issues/8911