XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Hub kubernetes recipe fails

    Scheduled Pinned Locked Moved Solved Advanced features
    6 Posts 2 Posters 337 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D Offline
      dingo
      last edited by

      freshly installed XCP-NG 8.3 and XOA deployed on it it, tried to deploy a simple k8s cluster from the Hub recipes for k8s, and it fails.

      it does deploy a master node, and then does nothing else, just sits there and spins for hours....

      any ideas ?

      1 Reply Last reply Reply Quote 0
      • D Offline
        dingo @olivierlambert
        last edited by

        @olivierlambert ok, that did work
        cluster deployed ok it seems, ill validate it all in the morning. thanks.

        debian@cp-1:~$ kubectl get pods --all-namespaces
NAMESPACE      NAME                           READY   STATUS    RESTARTS      AGE
kube-flannel   kube-flannel-ds-h2vj2          1/1     Running   0             34s
kube-flannel   kube-flannel-ds-j8s5t          1/1     Running   0             56s
kube-flannel   kube-flannel-ds-k2x5g          1/1     Running   0             107s
kube-flannel   kube-flannel-ds-nvl97          1/1     Running   0             11m
kube-flannel   kube-flannel-ds-qk748          1/1     Running   0             95s
kube-flannel   kube-flannel-ds-rqrgq          1/1     Running   0             48s
kube-flannel   kube-flannel-ds-ss7hx          1/1     Running   0             14m
kube-flannel   kube-flannel-ds-t5xt8          1/1     Running   0             6m2s
kube-system    coredns-5dd5756b68-rb82f       1/1     Running   0             14m
kube-system    coredns-5dd5756b68-rr9hb       1/1     Running   0             14m
kube-system    etcd-cp-1                      1/1     Running   0             14m
kube-system    etcd-cp-2                      1/1     Running   0             11m
kube-system    etcd-cp-3                      1/1     Running   0             6m1s
kube-system    kube-apiserver-cp-1            1/1     Running   0             14m
kube-system    kube-apiserver-cp-2            1/1     Running   0             11m
kube-system    kube-apiserver-cp-3            1/1     Running   0             5m59s
kube-system    kube-controller-manager-cp-1   1/1     Running   1 (11m ago)   14m
kube-system    kube-controller-manager-cp-2   1/1     Running   0             11m
kube-system    kube-controller-manager-cp-3   1/1     Running   0             5m58s
kube-system    kube-proxy-2w2df               1/1     Running   0             14m
kube-system    kube-proxy-6g7tt               1/1     Running   0             6m2s
kube-system    kube-proxy-h2mjc               1/1     Running   0             34s
kube-system    kube-proxy-lgvc9               1/1     Running   0             107s
kube-system    kube-proxy-pnvtg               1/1     Running   0             11m
kube-system    kube-proxy-rbg2l               1/1     Running   0             56s
kube-system    kube-proxy-v27b5               1/1     Running   0             95s
kube-system    kube-proxy-v5l7t               1/1     Running   0             48s
kube-system    kube-scheduler-cp-1            1/1     Running   1 (11m ago)   14m
kube-system    kube-scheduler-cp-2            1/1     Running   0             11m
kube-system    kube-scheduler-cp-3            1/1     Running   0             5m58s
kube-system    kube-vip-cp-1                  1/1     Running   1 (11m ago)   14m
kube-system    kube-vip-cp-2                  1/1     Running   0             11m
kube-system    kube-vip-cp-3                  1/1     Running   0             5m46s
debian@cp-1:~$ kubectl get nodes
NAME       STATUS   ROLES           AGE    VERSION
cp-1       Ready    control-plane   15m    v1.28.8
cp-2       Ready    control-plane   11m    v1.28.8
cp-3       Ready    control-plane   6m6s   v1.28.8
worker-1   Ready    <none>          99s    v1.28.8
worker-2   Ready    <none>          60s    v1.28.8
worker-3   Ready    <none>          52s    v1.28.8
worker-4   Ready    <none>          38s    v1.28.8
worker-5   Ready    <none>          111s   v1.28.8
        1 Reply Last reply Reply Quote 1
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          Hi,

          It's really hard to assist without knowing more. XOA release channel? Up to date? DHCP or static? Please provide the details so we can have a chance to help you…

          D 1 Reply Last reply Reply Quote 0
          • D Offline
            dingo @olivierlambert
            last edited by

            @olivierlambert Current version: 5.92.1 - XOA build: 20240401, XCP-
            NG 8.3, yes, everything by dhcp, what else can i say... its a brand new deployment

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              Can you try on latest release channel?

              D 1 Reply Last reply Reply Quote 0
              • D Offline
                dingo @olivierlambert
                last edited by

                @olivierlambert ok, that did work
                cluster deployed ok it seems, ill validate it all in the morning. thanks.

                debian@cp-1:~$ kubectl get pods --all-namespaces
NAMESPACE      NAME                           READY   STATUS    RESTARTS      AGE
kube-flannel   kube-flannel-ds-h2vj2          1/1     Running   0             34s
kube-flannel   kube-flannel-ds-j8s5t          1/1     Running   0             56s
kube-flannel   kube-flannel-ds-k2x5g          1/1     Running   0             107s
kube-flannel   kube-flannel-ds-nvl97          1/1     Running   0             11m
kube-flannel   kube-flannel-ds-qk748          1/1     Running   0             95s
kube-flannel   kube-flannel-ds-rqrgq          1/1     Running   0             48s
kube-flannel   kube-flannel-ds-ss7hx          1/1     Running   0             14m
kube-flannel   kube-flannel-ds-t5xt8          1/1     Running   0             6m2s
kube-system    coredns-5dd5756b68-rb82f       1/1     Running   0             14m
kube-system    coredns-5dd5756b68-rr9hb       1/1     Running   0             14m
kube-system    etcd-cp-1                      1/1     Running   0             14m
kube-system    etcd-cp-2                      1/1     Running   0             11m
kube-system    etcd-cp-3                      1/1     Running   0             6m1s
kube-system    kube-apiserver-cp-1            1/1     Running   0             14m
kube-system    kube-apiserver-cp-2            1/1     Running   0             11m
kube-system    kube-apiserver-cp-3            1/1     Running   0             5m59s
kube-system    kube-controller-manager-cp-1   1/1     Running   1 (11m ago)   14m
kube-system    kube-controller-manager-cp-2   1/1     Running   0             11m
kube-system    kube-controller-manager-cp-3   1/1     Running   0             5m58s
kube-system    kube-proxy-2w2df               1/1     Running   0             14m
kube-system    kube-proxy-6g7tt               1/1     Running   0             6m2s
kube-system    kube-proxy-h2mjc               1/1     Running   0             34s
kube-system    kube-proxy-lgvc9               1/1     Running   0             107s
kube-system    kube-proxy-pnvtg               1/1     Running   0             11m
kube-system    kube-proxy-rbg2l               1/1     Running   0             56s
kube-system    kube-proxy-v27b5               1/1     Running   0             95s
kube-system    kube-proxy-v5l7t               1/1     Running   0             48s
kube-system    kube-scheduler-cp-1            1/1     Running   1 (11m ago)   14m
kube-system    kube-scheduler-cp-2            1/1     Running   0             11m
kube-system    kube-scheduler-cp-3            1/1     Running   0             5m58s
kube-system    kube-vip-cp-1                  1/1     Running   1 (11m ago)   14m
kube-system    kube-vip-cp-2                  1/1     Running   0             11m
kube-system    kube-vip-cp-3                  1/1     Running   0             5m46s
debian@cp-1:~$ kubectl get nodes
NAME       STATUS   ROLES           AGE    VERSION
cp-1       Ready    control-plane   15m    v1.28.8
cp-2       Ready    control-plane   11m    v1.28.8
cp-3       Ready    control-plane   6m6s   v1.28.8
worker-1   Ready    <none>          99s    v1.28.8
worker-2   Ready    <none>          60s    v1.28.8
worker-3   Ready    <none>          52s    v1.28.8
worker-4   Ready    <none>          38s    v1.28.8
worker-5   Ready    <none>          111s   v1.28.8
                1 Reply Last reply Reply Quote 1
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  Okay so it's possible we fixed something in latest, it will be in stable in 3 weeks 🙂

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO olivierlambert marked this topic as a question on
                  • olivierlambertO olivierlambert has marked this topic as solved on
                  • First post
                    Last post