Skip to content

Commit

Permalink
Update Conformance Results for v1.25/alvistack-vagrant-kubernetes (#2468
Browse files Browse the repository at this point in the history 
)

Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
  • Loading branch information
@hswong3i
hswong3i authored Mar 2, 2023
1 parent f6d8785 commit d8b1d80
Show file tree
Hide file tree
Showing 4 changed files with 36,359 additions and 35,407 deletions.
2 changes: 1 addition & 1 deletion v1.25/alvistack-vagrant-kubernetes/PRODUCT.yaml
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
vendor: AlviStack
name: AlviStack - Vagrant Box Packaging for Kubernetes
version: 20221213.1.1
version: 20230225.1.1
website_url: https://github.com/alvistack/vagrant-kubernetes
documentation_url: https://github.com/alvistack/ansible-collection-kubernetes/tree/master/docs
product_logo_url: https://raw.githubusercontent.com/alvistack/ansible-collection-kubernetes/master/docs/images/alvistack/stacked/color/alvistack-stacked-color.svg
Expand Down
106 changes: 55 additions & 51 deletions v1.25/alvistack-vagrant-kubernetes/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,33 +4,33 @@ For running k8s conformance test we need 2 vagrant instances as master
and 1 vagrant instance as node with following minimal system
requirement, e.g.

- host
- libvirt
- nested virtualization enabled
- Ubuntu 22.04
- 8 CPUs
- 32GB RAM
- `kube01`
- kubernetes master, etcd
- cri-o, flannel
- Ubuntu 22.04
- IP: 192.168.121.101/24
- 2 CPUs
- 8GB RAM
- `kube02`
- kubernetes master, etcd
- cri-o, flannel
- Ubuntu 22.04
- IP: 192.168.121.102/24
- 2 CPUs
- 8GB RAM
- `kube03`
- kubernetes node, etcd
- cri-o, flannel
- Ubuntu 22.04
- IP: 192.168.121.103/24
- 2 CPUs
- 8GB RAM
- host
- libvirt
- nested virtualization enabled
- Ubuntu 22.04
- 8 CPUs
- 32GB RAM
- `kube01`
- kubernetes master, etcd
- cri-o, cilium
- Ubuntu 22.04
- IP: 192.168.121.101/24
- 2 CPUs
- 8GB RAM
- `kube02`
- kubernetes master, etcd
- cri-o, cilium
- Ubuntu 22.04
- IP: 192.168.121.102/24
- 2 CPUs
- 8GB RAM
- `kube03`
- kubernetes node, etcd
- cri-o, cilium
- Ubuntu 22.04
- IP: 192.168.121.103/24
- 2 CPUs
- 8GB RAM

## Bootstrap Host

Expand Down Expand Up @@ -99,37 +99,41 @@ All instances could be SSH and switch as root with `sudo su -`, e.g.
Check result:

root@kube01:~# kubectl get node
NAME STATUS ROLES AGE VERSION
kube01 Ready control-plane,master 9m38s v1.25.5
kube02 Ready control-plane,master 8m32s v1.25.5
kube03 Ready <none> 8m14s v1.25.5
NAME STATUS ROLES AGE VERSION
kube01 Ready control-plane 3h41m v1.25.6
kube02 Ready control-plane 3h40m v1.25.6
kube03 Ready <none> 3h36m v1.25.6

root@kube01:~# kubectl get pod --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-flannel kube-flannel-ds-5z9q7 1/1 Running 0 70s
kube-flannel kube-flannel-ds-7bf94 1/1 Running 0 70s
kube-flannel kube-flannel-ds-99tj8 1/1 Running 0 70s
kube-system coredns-bd6b6df9f-cqzkx 1/1 Running 0 70s
kube-system coredns-bd6b6df9f-tcv7m 1/1 Running 0 70s
kube-system kube-addon-manager-kube01 1/1 Running 2 80s
kube-system kube-addon-manager-kube02 1/1 Running 2 80s
kube-system kube-apiserver-kube01 1/1 Running 3 80s
kube-system kube-apiserver-kube02 1/1 Running 3 80s
kube-system kube-controller-manager-kube01 1/1 Running 3 80s
kube-system kube-controller-manager-kube02 1/1 Running 4 80s
kube-system kube-proxy-brwdv 1/1 Running 0 70s
kube-system kube-proxy-ppn7b 1/1 Running 0 70s
kube-system kube-proxy-qn7vg 1/1 Running 0 70s
kube-system kube-scheduler-kube01 1/1 Running 3 80s
kube-system kube-scheduler-kube02 1/1 Running 4 80s
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system cilium-2cncz 1/1 Running 0 3h36m
kube-system cilium-9tkfg 1/1 Running 0 3h39m
kube-system cilium-node-init-8b7n2 1/1 Running 0 3h39m
kube-system cilium-node-init-979mb 1/1 Running 0 3h36m
kube-system cilium-node-init-s84z5 1/1 Running 0 3h39m
kube-system cilium-operator-59d7d77cdc-lppbd 1/1 Running 0 3h39m
kube-system cilium-r4lc4 1/1 Running 0 3h39m
kube-system coredns-565d847f94-5nh2n 1/1 Running 0 3h38m
kube-system coredns-565d847f94-qqvf6 1/1 Running 0 3h38m
kube-system kube-addon-manager-kube01 1/1 Running 0 3h40m
kube-system kube-addon-manager-kube02 1/1 Running 0 3h40m
kube-system kube-apiserver-kube01 1/1 Running 0 3h41m
kube-system kube-apiserver-kube02 1/1 Running 0 3h40m
kube-system kube-controller-manager-kube01 1/1 Running 0 3h41m
kube-system kube-controller-manager-kube02 1/1 Running 0 3h40m
kube-system kube-proxy-22s9q 1/1 Running 0 3h36m
kube-system kube-proxy-cm4qg 1/1 Running 0 3h40m
kube-system kube-proxy-d66m7 1/1 Running 0 3h40m
kube-system kube-scheduler-kube01 1/1 Running 0 3h41m
kube-system kube-scheduler-kube02 1/1 Running 0 3h40m

## Run Sonobuoy

Run sonobuoy for conformance test as official procedure
(<https://github.com/cncf/k8s-conformance/blob/master/instructions.md>):

root@kube01:~# sonobuoy run --mode=certified-conformance

root@kube01:~# sonobuoy status

root@kube01:~# sonobuoy retrieve
Loading

0 comments on commit d8b1d80

Please sign in to comment.