search

praveenkumar / minp

Microshift in container
2 stars 0 forks source link

Flannel not being created on the cluster #1

Open vyasgun opened 3 weeks ago

vyasgun commented 3 weeks ago

Followed the steps in minp README

wsl version with cgroup2fs enabled

PS C:\Users\gvyas> wsl --version
WSL version: 2.3.24.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22621.4317

PS C:\Users\gvyas> podman run -it --rm spurin/wsl-cgroupsv2:latest
Success: cgroup type is cgroup2fs

Details of the podman machine

PS C:\Users\gvyas> podman machine ls
NAME        VM TYPE     CREATED            LAST UP            CPUS        MEMORY      DISK SIZE
vm2*        wsl         About an hour ago  Currently running  10          2GiB        100GiB
vm1         wsl         6 days ago         6 days ago         10          2GiB        100GiB
PS C:\Users\gvyas> podman machine inspect vm2
[
     {
          "ConfigDir": {
               "Path": "C:\\Users\\gvyas\\.config\\containers\\podman\\machine\\wsl"
          },
          "ConnectionInfo": {
               "PodmanSocket": {
                    "Path": "C:\\Users\\gvyas\\AppData\\Local\\Temp\\podman\\vm2-api.sock"
               },
               "PodmanPipe": {
                    "Path": "\\\\.\\pipe\\podman-vm2"
               }
          },
          "Created": "2024-11-04T15:15:47.2545796+05:30",
          "LastUp": "2024-11-04T15:22:41.6174458+05:30",
          "Name": "vm2",
          "Resources": {
               "CPUs": 10,
               "DiskSize": 100,
               "Memory": 2048,
               "USBs": []
          },
          "SSHConfig": {
               "IdentityPath": "C:\\Users\\gvyas\\.local\\share\\containers\\podman\\machine\\machine",
               "Port": 22415,
               "RemoteUsername": "user"
          },
          "State": "running",
          "UserModeNetworking": false,
          "Rootful": true,
          "Rosetta": false
     }
]

On inspecting the existing pods, the flannel deployment has not been created which is causing all the pods to remainstuck in Pending

PS C:\Users\gvyas> oc.exe --kubeconfig=.\tmp\kubeconfig get deploy -A
NAMESPACE              NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system            csi-snapshot-controller   0/1     1            0           52m
kube-system            csi-snapshot-webhook      0/1     1            0           52m
openshift-ingress      router-default            0/1     1            0           52m
openshift-service-ca   service-ca                0/1     1            0           52m
PS C:\Users\gvyas> oc.exe --kubeconfig=.\tmp\kubeconfig get pod -A
NAMESPACE              NAME                                       READY   STATUS    RESTARTS   AGE
kube-system            csi-snapshot-controller-7c8c9f547f-8mc4d   0/1     Pending   0          52m
kube-system            csi-snapshot-webhook-594f8ccbd7-v67xs      0/1     Pending   0          52m
openshift-ingress      router-default-6b55ddd567-2wnm4            0/1     Pending   0          50m
openshift-service-ca   service-ca-8bfc7d879-4vjx4                 0/1     Pending   0          50m

On inspecting the microshift logs

bash-5.1# journalctl -u microshift | grep E11 | grep flannel
Nov 04 10:06:34 127.0.0.1.nip.io microshift[878]: cluster-policy-controller E1104 10:06:34.851531     878 podsecurity_label_sync_controller.go:420] failed to determine whether namespace "kube-flannel" should be enqueued: namespace "kube-flannel" not found
Nov 04 10:06:34 127.0.0.1.nip.io microshift[878]: cluster-policy-controller E1104 10:06:34.851641     878 podsecurity_label_sync_controller.go:420] failed to determine whether namespace "kube-flannel" should be enqueued: namespace "kube-flannel" not found
Nov 04 10:08:05 127.0.0.1.nip.io microshift[1769]: cluster-policy-controller E1104 10:08:05.294486    1769 podsecurity_label_sync_controller.go:420] failed to determine whether namespace "kube-flannel" should be enqueued: namespace "kube-flannel" not found
Nov 04 10:08:05 127.0.0.1.nip.io microshift[1769]: cluster-policy-controller E1104 10:08:05.294564    1769 podsecurity_label_sync_controller.go:420] failed to determine whether namespace "kube-flannel" should be enqueued: namespace "kube-flannel" not found
Nov 04 10:08:17 127.0.0.1.nip.io microshift[1881]: cluster-policy-controller E1104 10:08:17.314598    1881 podsecurity_label_sync_controller.go:420] failed to determine whether namespace "kube-flannel" should be enqueued: namespace "kube-flannel" not found
...
praveenkumar commented 3 weeks ago

I went through same steps and having same version of wsl but not able to reproduce this on a fresh installed windows system and latest podman-desktop

> wsl.exe --version
WSL version: 2.3.24.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4317

> kubectl --kubeconfig=kubeconfig get pods -A
NAMESPACE              NAME                                       READY   STATUS    RESTARTS        AGE
kube-flannel           kube-flannel-ds-m4bg9                      1/1     Running   1 (4m32s ago)   5m28s
kube-proxy             kube-proxy-v9xwg                           1/1     Running   0               5m27s
kube-system            csi-snapshot-controller-7c8c9f547f-472sc   1/1     Running   0               5m35s
kube-system            csi-snapshot-webhook-594f8ccbd7-gnmqf      1/1     Running   0               5m38s
openshift-dns          dns-default-5zxkz                          2/2     Running   0               5m3s
openshift-dns          node-resolver-r5zjs                        1/1     Running   0               5m28s
openshift-ingress      router-default-f57574787-k8bdx             1/1     Running   0               5m35s
openshift-service-ca   service-ca-8bfc7d879-lhqcg                 1/1     Running   0               5m35s