You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Raihan Jana Prasetya <ra...@gmail.com> on 2023/10/11 02:59:10 UTC
Create Kubernetes Cluster Problem
Hello,
I have a problem when creating Kubernetes cluster on apache cloudstack
version 1.18.1 with this Kubernetes version
1.27.2, kubernetes version, see
https://github.com/kubernetes/kubernetes/releases
1.3.0, CNI version, see https://github.com/containernetworking/plugins/releases
1.27.0, cri-tools version, see
https://github.com/kubernetes-sigs/cri-tools/releases
1.11, weave addon *for* kubernetes, see
https://github.com/weaveworks/weave/tree/master/prog/weave-kube
2.7.0, kubernetes dashboard version, see
https://github.com/kubernetes/dashboard/release
the cluster always fails to start, but the control and regular nodes is
running. This is the issue I found when I check the pods
skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
--all-namespaces
NAMESPACE
NAME READY
STATUS RESTARTS AGE
kube-system
coredns-5d78c9869d-ckm89 0/1
Pending 0 12h
kube-system
coredns-5d78c9869d-spn7x 0/1
Pending 0 12h
kube-system
etcd-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-apiserver-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-proxy-s9jv8 1/1
Running 1 (32m ago) 12h
kube-system
kube-proxy-zvml6 1/1
Running 1 (32m ago) 12h
kube-system
kube-scheduler-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
weave-net-hcsql 0/2
Init:ImagePullBackOff 0 12h
kube-system
weave-net-xnq5k 0/2
Init:ImagePullBackOff 0 12h
kubernetes-dashboard
dashboard-metrics-scraper-5cb4f4bb9c-ljrh4 0/1
Pending 0 12h
kubernetes-dashboard
kubernetes-dashboard-6967859bff-b9lm5 0/1
Pending 0 12h
When i want to check the pods, it says that i need to be logged in to the
server
skripsi@cloudstack:~$ kubectl describe pod weave-net-hcsql
E1011 02:30:01.456779 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.457860 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.458810 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.460754 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.462716 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
error: You must be logged in to the server (the server has asked for the
client to provide credentials)
Can you please guide me what should i do. thank you :)
Re: Create Kubernetes Cluster Problem
Posted by Raihan Jana Prasetya <ra...@gmail.com>.
Hi again,
thank's for your reply again. i've managed to get the cluster running yay.
i didn't change any configuration, i believe i've done it correctly since
the beginning. i don't know what solves all of the problems, i just
restarted the server a few times after it runs for a few hours and
eventually the cluster is now running.
For the next step after the cluster is running, i'm still confused on how
to get another IP that expose the dashboard. In this video
https://youtu.be/zNYtsVhuIgQ?si=9EVLJe2uS8nycGG8&t=938 i found that i need
to run this command
kubectl --kubeconfig kube.conf apply -f metrics.yaml and
kubectl --kubeconfig kube.conf apply -f nginx-ingress-controller-.yaml
but i don't have the yaml file. what should i do?
Thank you
Regards,
Raihan
On Thu, Oct 12, 2023 at 3:56 PM Kiran Chavala <ki...@shapeblue.com>
wrote:
> Hi Raihan
>
> Yes the value of endpoint.url should be
> http://192.168.10.120:8080/client/api
>
> Regards
> Kiran
>
>
> From: Raihan Jana Prasetya <ra...@gmail.com>
> Date: Thursday, 12 October 2023 at 1:45 PM
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Subject: Re: Create Kubernetes Cluster Problem
> in the global settings i need to set the value of the endpoint.url. i
> accessed my apache cloudstack from 192.168.10.120:8080/client, does it
> mean
> the value of the endpoint.url should be 192.168.10.120:8080/client/api ?
> thank you
>
> On Thu, Oct 12, 2023 at 10:49 AM Raihan Jana Prasetya <
> raihanjanaprasetya@gmail.com> wrote:
>
> > Hi Kiran,
> >
> > Thank you for the respond. yes i have used the same command to generate
> > the ISO. Last night i turned off the server, and this morning i checked,
> > all of the pods are now running, but NOT READY yet. I think restart made
> > them running now.
> > The issue i'm facing now is, i'm trying to start the k8s cluster again
> > from the UI, but it's been 40 minutes on the "SCHEDULED" state on the
> > "Events" tab and the state of the cluster and on the Kubernetes tab the
> > state of the cluster is "Error". I've run this command too:
> >
> > skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf create
> > serviceaccount dashboard-admin-sa
> > serviceaccount/dashboard-admin-sa created
> > skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf create
> > clusterrolebinding dashboard-admin-sa --clusterrole=cluster-admin
> > --serviceaccount=default:dashboard-admin-sa
> > clusterrolebinding.rbac.authorization.k8s.io/dashboard-admin-sa created
> > *creating token*
> >
> > skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get nodes
> > --all-namespaces
> > NAME STATUS ROLES AGE VERSION
> > k8s-k8s-1272-control-18b19d3c77f Ready control-plane 37h v1.27.2
> > k8s-k8s-1272-node-18b19d40e2b Ready <none> 37h v1.27.2
> >
> > skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
> > --all-namespaces
> > NAMESPACE NAME
> > READY STATUS RESTARTS AGE
> > kube-system coredns-5d78c9869d-ckm89
> > 1/1 Running 1 (<invalid> ago) 37h
> > kube-system coredns-5d78c9869d-spn7x
> > 1/1 Running 1 (<invalid> ago) 37h
> > kube-system etcd-k8s-k8s-1272-control-18b19d3c77f
> > 0/1 Running 3 (<invalid> ago) 37h
> > kube-system kube-apiserver-k8s-k8s-1272-control-18b19d3c77f
> > 0/1 Running 3 (<invalid> ago) 37h
> > kube-system
> > kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 0/1
> Running
> > 3 (<invalid> ago) 37h
> > kube-system kube-proxy-s9jv8
> > 1/1 Running 3 (<invalid> ago) 37h
> > kube-system kube-proxy-zvml6
> > 1/1 Running 3 (<invalid> ago) 37h
> > kube-system kube-scheduler-k8s-k8s-1272-control-18b19d3c77f
> > 0/1 Running 3 (<invalid> ago) 37h
> > kube-system weave-net-hcsql
> > 2/2 Running 3 (<invalid> ago) 37h
> > kube-system weave-net-xnq5k
> > 2/2 Running 3 (<invalid> ago) 37h
> > kubernetes-dashboard dashboard-metrics-scraper-5cb4f4bb9c-ljrh4
> > 1/1 Running 1 (<invalid> ago) 37h
> > kubernetes-dashboard kubernetes-dashboard-6967859bff-b9lm5
> > 1/1 Running 1 (<invalid> ago) 37h
> >
> > Regards,
> > Raihan
> >
> > On Wed, Oct 11, 2023 at 6:06 PM Kiran Chavala <
> kiran.chavala@shapeblue.com>
> > wrote:
> >
> >> Hi Raihan
> >>
> >> I was able to launch a working k8s cluster successfully after generating
> >> the iso for 1.2.7.2
> >>
> >> Please use the following command to generate the ISO
> >>
> >> ./create-kubernetes-binaries-iso.sh ./ 1.27.2 1.3.0 1.27.0
> >>
> https://raw.githubusercontent.com/weaveworks/weave/master/prog/weave-kube/weave-daemonset-k8s-1.11.yaml
> >>
> https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml
> >> setup-1.27.2<
> >>
> https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml%20setup-1.27.2
> >> >
> >>
> >> Regards
> >> Kiran
> >>
> >> From: Kiran Chavala <ki...@shapeblue.com>
> >> Date: Wednesday, 11 October 2023 at 3:32 PM
> >> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> >> Subject: Re: Create Kubernetes Cluster Problem
> >> Hi Raihan
> >>
> >>
> >> Could you use the community generated Kubernetes iso
> >>
> >> https://download.cloudstack.org/cks/setup-1.27.3.iso
> >>
> >>
> >> Meanwhile I will cross check with 1.27.2 version locally and let you
> know
> >> if I can reproduce the issue
> >>
> >> Regards
> >> Kiran
> >>
> >> From: Raihan Jana Prasetya <ra...@gmail.com>
> >> Date: Wednesday, 11 October 2023 at 8:30 AM
> >> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> >> Subject: Create Kubernetes Cluster Problem
> >> Hello,
> >>
> >> I have a problem when creating Kubernetes cluster on apache cloudstack
> >> version 1.18.1 with this Kubernetes version
> >> 1.27.2, kubernetes version, see
> >> https://github.com/kubernetes/kubernetes/releases
> >>
> >> 1.3.0, CNI version, see
> >> https://github.com/containernetworking/plugins/releases
> >>
> >> 1.27.0, cri-tools version, see
> >> https://github.com/kubernetes-sigs/cri-tools/releases
> >>
> >> 1.11, weave addon *for* kubernetes, see
> >> https://github.com/weaveworks/weave/tree/master/prog/weave-kube
> >>
> >> 2.7.0, kubernetes dashboard version, see
> >> https://github.com/kubernetes/dashboard/release
> >>
> >>
> >> the cluster always fails to start, but the control and regular nodes is
> >> running. This is the issue I found when I check the pods
> >>
> >> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
> >> --all-namespaces
> >>
> >> NAMESPACE
> >> NAME READY
> >> STATUS RESTARTS AGE
> >>
> >> kube-system
> >> coredns-5d78c9869d-ckm89 0/1
> >> Pending 0 12h
> >>
> >> kube-system
> >> coredns-5d78c9869d-spn7x 0/1
> >> Pending 0 12h
> >>
> >> kube-system
> >> etcd-k8s-k8s-1272-control-18b19d3c77f 1/1
> >> Running 1 (32m ago) 12h
> >>
> >> kube-system
> >> kube-apiserver-k8s-k8s-1272-control-18b19d3c77f 1/1
> >> Running 1 (32m ago) 12h
> >>
> >> kube-system
> >> kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 1/1
> >> Running 1 (32m ago) 12h
> >>
> >> kube-system
> >> kube-proxy-s9jv8 1/1
> >> Running 1 (32m ago) 12h
> >>
> >> kube-system
> >> kube-proxy-zvml6 1/1
> >> Running 1 (32m ago) 12h
> >>
> >> kube-system
> >> kube-scheduler-k8s-k8s-1272-control-18b19d3c77f 1/1
> >> Running 1 (32m ago) 12h
> >>
> >> kube-system
> >> weave-net-hcsql 0/2
> >> Init:ImagePullBackOff 0 12h
> >>
> >> kube-system
> >> weave-net-xnq5k 0/2
> >> Init:ImagePullBackOff 0 12h
> >>
> >> kubernetes-dashboard
> >> dashboard-metrics-scraper-5cb4f4bb9c-ljrh4 0/1
> >> Pending 0 12h
> >>
> >> kubernetes-dashboard
> >> kubernetes-dashboard-6967859bff-b9lm5 0/1
> >> Pending 0 12h
> >>
> >> When i want to check the pods, it says that i need to be logged in to
> the
> >> server
> >>
> >> skripsi@cloudstack:~$ kubectl describe pod weave-net-hcsql
> >>
> >> E1011 02:30:01.456779 23642 memcache.go:265] couldn't get current
> server
> >> API group list: the server has asked for the client to provide
> credentials
> >>
> >> E1011 02:30:01.457860 23642 memcache.go:265] couldn't get current
> server
> >> API group list: the server has asked for the client to provide
> credentials
> >>
> >> E1011 02:30:01.458810 23642 memcache.go:265] couldn't get current
> server
> >> API group list: the server has asked for the client to provide
> credentials
> >>
> >> E1011 02:30:01.460754 23642 memcache.go:265] couldn't get current
> server
> >> API group list: the server has asked for the client to provide
> credentials
> >>
> >> E1011 02:30:01.462716 23642 memcache.go:265] couldn't get current
> server
> >> API group list: the server has asked for the client to provide
> credentials
> >>
> >> error: You must be logged in to the server (the server has asked for the
> >> client to provide credentials)
> >>
> >> Can you please guide me what should i do. thank you :)
> >>
> >>
> >>
> >>
> >>
> >>
>
>
>
>
Re: Create Kubernetes Cluster Problem
Posted by Kiran Chavala <ki...@shapeblue.com>.
Hi Raihan
Yes the value of endpoint.url should be http://192.168.10.120:8080/client/api
Regards
Kiran
From: Raihan Jana Prasetya <ra...@gmail.com>
Date: Thursday, 12 October 2023 at 1:45 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Re: Create Kubernetes Cluster Problem
in the global settings i need to set the value of the endpoint.url. i
accessed my apache cloudstack from 192.168.10.120:8080/client, does it mean
the value of the endpoint.url should be 192.168.10.120:8080/client/api ?
thank you
On Thu, Oct 12, 2023 at 10:49 AM Raihan Jana Prasetya <
raihanjanaprasetya@gmail.com> wrote:
> Hi Kiran,
>
> Thank you for the respond. yes i have used the same command to generate
> the ISO. Last night i turned off the server, and this morning i checked,
> all of the pods are now running, but NOT READY yet. I think restart made
> them running now.
> The issue i'm facing now is, i'm trying to start the k8s cluster again
> from the UI, but it's been 40 minutes on the "SCHEDULED" state on the
> "Events" tab and the state of the cluster and on the Kubernetes tab the
> state of the cluster is "Error". I've run this command too:
>
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf create
> serviceaccount dashboard-admin-sa
> serviceaccount/dashboard-admin-sa created
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf create
> clusterrolebinding dashboard-admin-sa --clusterrole=cluster-admin
> --serviceaccount=default:dashboard-admin-sa
> clusterrolebinding.rbac.authorization.k8s.io/dashboard-admin-sa created
> *creating token*
>
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get nodes
> --all-namespaces
> NAME STATUS ROLES AGE VERSION
> k8s-k8s-1272-control-18b19d3c77f Ready control-plane 37h v1.27.2
> k8s-k8s-1272-node-18b19d40e2b Ready <none> 37h v1.27.2
>
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
> --all-namespaces
> NAMESPACE NAME
> READY STATUS RESTARTS AGE
> kube-system coredns-5d78c9869d-ckm89
> 1/1 Running 1 (<invalid> ago) 37h
> kube-system coredns-5d78c9869d-spn7x
> 1/1 Running 1 (<invalid> ago) 37h
> kube-system etcd-k8s-k8s-1272-control-18b19d3c77f
> 0/1 Running 3 (<invalid> ago) 37h
> kube-system kube-apiserver-k8s-k8s-1272-control-18b19d3c77f
> 0/1 Running 3 (<invalid> ago) 37h
> kube-system
> kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 0/1 Running
> 3 (<invalid> ago) 37h
> kube-system kube-proxy-s9jv8
> 1/1 Running 3 (<invalid> ago) 37h
> kube-system kube-proxy-zvml6
> 1/1 Running 3 (<invalid> ago) 37h
> kube-system kube-scheduler-k8s-k8s-1272-control-18b19d3c77f
> 0/1 Running 3 (<invalid> ago) 37h
> kube-system weave-net-hcsql
> 2/2 Running 3 (<invalid> ago) 37h
> kube-system weave-net-xnq5k
> 2/2 Running 3 (<invalid> ago) 37h
> kubernetes-dashboard dashboard-metrics-scraper-5cb4f4bb9c-ljrh4
> 1/1 Running 1 (<invalid> ago) 37h
> kubernetes-dashboard kubernetes-dashboard-6967859bff-b9lm5
> 1/1 Running 1 (<invalid> ago) 37h
>
> Regards,
> Raihan
>
> On Wed, Oct 11, 2023 at 6:06 PM Kiran Chavala <ki...@shapeblue.com>
> wrote:
>
>> Hi Raihan
>>
>> I was able to launch a working k8s cluster successfully after generating
>> the iso for 1.2.7.2
>>
>> Please use the following command to generate the ISO
>>
>> ./create-kubernetes-binaries-iso.sh ./ 1.27.2 1.3.0 1.27.0
>> https://raw.githubusercontent.com/weaveworks/weave/master/prog/weave-kube/weave-daemonset-k8s-1.11.yaml
>> https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml
>> setup-1.27.2<
>> https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml%20setup-1.27.2
>> >
>>
>> Regards
>> Kiran
>>
>> From: Kiran Chavala <ki...@shapeblue.com>
>> Date: Wednesday, 11 October 2023 at 3:32 PM
>> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
>> Subject: Re: Create Kubernetes Cluster Problem
>> Hi Raihan
>>
>>
>> Could you use the community generated Kubernetes iso
>>
>> https://download.cloudstack.org/cks/setup-1.27.3.iso
>>
>>
>> Meanwhile I will cross check with 1.27.2 version locally and let you know
>> if I can reproduce the issue
>>
>> Regards
>> Kiran
>>
>> From: Raihan Jana Prasetya <ra...@gmail.com>
>> Date: Wednesday, 11 October 2023 at 8:30 AM
>> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
>> Subject: Create Kubernetes Cluster Problem
>> Hello,
>>
>> I have a problem when creating Kubernetes cluster on apache cloudstack
>> version 1.18.1 with this Kubernetes version
>> 1.27.2, kubernetes version, see
>> https://github.com/kubernetes/kubernetes/releases
>>
>> 1.3.0, CNI version, see
>> https://github.com/containernetworking/plugins/releases
>>
>> 1.27.0, cri-tools version, see
>> https://github.com/kubernetes-sigs/cri-tools/releases
>>
>> 1.11, weave addon *for* kubernetes, see
>> https://github.com/weaveworks/weave/tree/master/prog/weave-kube
>>
>> 2.7.0, kubernetes dashboard version, see
>> https://github.com/kubernetes/dashboard/release
>>
>>
>> the cluster always fails to start, but the control and regular nodes is
>> running. This is the issue I found when I check the pods
>>
>> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
>> --all-namespaces
>>
>> NAMESPACE
>> NAME READY
>> STATUS RESTARTS AGE
>>
>> kube-system
>> coredns-5d78c9869d-ckm89 0/1
>> Pending 0 12h
>>
>> kube-system
>> coredns-5d78c9869d-spn7x 0/1
>> Pending 0 12h
>>
>> kube-system
>> etcd-k8s-k8s-1272-control-18b19d3c77f 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-apiserver-k8s-k8s-1272-control-18b19d3c77f 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-proxy-s9jv8 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-proxy-zvml6 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-scheduler-k8s-k8s-1272-control-18b19d3c77f 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> weave-net-hcsql 0/2
>> Init:ImagePullBackOff 0 12h
>>
>> kube-system
>> weave-net-xnq5k 0/2
>> Init:ImagePullBackOff 0 12h
>>
>> kubernetes-dashboard
>> dashboard-metrics-scraper-5cb4f4bb9c-ljrh4 0/1
>> Pending 0 12h
>>
>> kubernetes-dashboard
>> kubernetes-dashboard-6967859bff-b9lm5 0/1
>> Pending 0 12h
>>
>> When i want to check the pods, it says that i need to be logged in to the
>> server
>>
>> skripsi@cloudstack:~$ kubectl describe pod weave-net-hcsql
>>
>> E1011 02:30:01.456779 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> E1011 02:30:01.457860 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> E1011 02:30:01.458810 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> E1011 02:30:01.460754 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> E1011 02:30:01.462716 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> error: You must be logged in to the server (the server has asked for the
>> client to provide credentials)
>>
>> Can you please guide me what should i do. thank you :)
>>
>>
>>
>>
>>
>>
Re: Create Kubernetes Cluster Problem
Posted by Raihan Jana Prasetya <ra...@gmail.com>.
in the global settings i need to set the value of the endpoint.url. i
accessed my apache cloudstack from 192.168.10.120:8080/client, does it mean
the value of the endpoint.url should be 192.168.10.120:8080/client/api ?
thank you
On Thu, Oct 12, 2023 at 10:49 AM Raihan Jana Prasetya <
raihanjanaprasetya@gmail.com> wrote:
> Hi Kiran,
>
> Thank you for the respond. yes i have used the same command to generate
> the ISO. Last night i turned off the server, and this morning i checked,
> all of the pods are now running, but NOT READY yet. I think restart made
> them running now.
> The issue i'm facing now is, i'm trying to start the k8s cluster again
> from the UI, but it's been 40 minutes on the "SCHEDULED" state on the
> "Events" tab and the state of the cluster and on the Kubernetes tab the
> state of the cluster is "Error". I've run this command too:
>
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf create
> serviceaccount dashboard-admin-sa
> serviceaccount/dashboard-admin-sa created
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf create
> clusterrolebinding dashboard-admin-sa --clusterrole=cluster-admin
> --serviceaccount=default:dashboard-admin-sa
> clusterrolebinding.rbac.authorization.k8s.io/dashboard-admin-sa created
> *creating token*
>
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get nodes
> --all-namespaces
> NAME STATUS ROLES AGE VERSION
> k8s-k8s-1272-control-18b19d3c77f Ready control-plane 37h v1.27.2
> k8s-k8s-1272-node-18b19d40e2b Ready <none> 37h v1.27.2
>
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
> --all-namespaces
> NAMESPACE NAME
> READY STATUS RESTARTS AGE
> kube-system coredns-5d78c9869d-ckm89
> 1/1 Running 1 (<invalid> ago) 37h
> kube-system coredns-5d78c9869d-spn7x
> 1/1 Running 1 (<invalid> ago) 37h
> kube-system etcd-k8s-k8s-1272-control-18b19d3c77f
> 0/1 Running 3 (<invalid> ago) 37h
> kube-system kube-apiserver-k8s-k8s-1272-control-18b19d3c77f
> 0/1 Running 3 (<invalid> ago) 37h
> kube-system
> kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 0/1 Running
> 3 (<invalid> ago) 37h
> kube-system kube-proxy-s9jv8
> 1/1 Running 3 (<invalid> ago) 37h
> kube-system kube-proxy-zvml6
> 1/1 Running 3 (<invalid> ago) 37h
> kube-system kube-scheduler-k8s-k8s-1272-control-18b19d3c77f
> 0/1 Running 3 (<invalid> ago) 37h
> kube-system weave-net-hcsql
> 2/2 Running 3 (<invalid> ago) 37h
> kube-system weave-net-xnq5k
> 2/2 Running 3 (<invalid> ago) 37h
> kubernetes-dashboard dashboard-metrics-scraper-5cb4f4bb9c-ljrh4
> 1/1 Running 1 (<invalid> ago) 37h
> kubernetes-dashboard kubernetes-dashboard-6967859bff-b9lm5
> 1/1 Running 1 (<invalid> ago) 37h
>
> Regards,
> Raihan
>
> On Wed, Oct 11, 2023 at 6:06 PM Kiran Chavala <ki...@shapeblue.com>
> wrote:
>
>> Hi Raihan
>>
>> I was able to launch a working k8s cluster successfully after generating
>> the iso for 1.2.7.2
>>
>> Please use the following command to generate the ISO
>>
>> ./create-kubernetes-binaries-iso.sh ./ 1.27.2 1.3.0 1.27.0
>> https://raw.githubusercontent.com/weaveworks/weave/master/prog/weave-kube/weave-daemonset-k8s-1.11.yaml
>> https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml
>> setup-1.27.2<
>> https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml%20setup-1.27.2
>> >
>>
>> Regards
>> Kiran
>>
>> From: Kiran Chavala <ki...@shapeblue.com>
>> Date: Wednesday, 11 October 2023 at 3:32 PM
>> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
>> Subject: Re: Create Kubernetes Cluster Problem
>> Hi Raihan
>>
>>
>> Could you use the community generated Kubernetes iso
>>
>> https://download.cloudstack.org/cks/setup-1.27.3.iso
>>
>>
>> Meanwhile I will cross check with 1.27.2 version locally and let you know
>> if I can reproduce the issue
>>
>> Regards
>> Kiran
>>
>> From: Raihan Jana Prasetya <ra...@gmail.com>
>> Date: Wednesday, 11 October 2023 at 8:30 AM
>> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
>> Subject: Create Kubernetes Cluster Problem
>> Hello,
>>
>> I have a problem when creating Kubernetes cluster on apache cloudstack
>> version 1.18.1 with this Kubernetes version
>> 1.27.2, kubernetes version, see
>> https://github.com/kubernetes/kubernetes/releases
>>
>> 1.3.0, CNI version, see
>> https://github.com/containernetworking/plugins/releases
>>
>> 1.27.0, cri-tools version, see
>> https://github.com/kubernetes-sigs/cri-tools/releases
>>
>> 1.11, weave addon *for* kubernetes, see
>> https://github.com/weaveworks/weave/tree/master/prog/weave-kube
>>
>> 2.7.0, kubernetes dashboard version, see
>> https://github.com/kubernetes/dashboard/release
>>
>>
>> the cluster always fails to start, but the control and regular nodes is
>> running. This is the issue I found when I check the pods
>>
>> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
>> --all-namespaces
>>
>> NAMESPACE
>> NAME READY
>> STATUS RESTARTS AGE
>>
>> kube-system
>> coredns-5d78c9869d-ckm89 0/1
>> Pending 0 12h
>>
>> kube-system
>> coredns-5d78c9869d-spn7x 0/1
>> Pending 0 12h
>>
>> kube-system
>> etcd-k8s-k8s-1272-control-18b19d3c77f 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-apiserver-k8s-k8s-1272-control-18b19d3c77f 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-proxy-s9jv8 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-proxy-zvml6 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> kube-scheduler-k8s-k8s-1272-control-18b19d3c77f 1/1
>> Running 1 (32m ago) 12h
>>
>> kube-system
>> weave-net-hcsql 0/2
>> Init:ImagePullBackOff 0 12h
>>
>> kube-system
>> weave-net-xnq5k 0/2
>> Init:ImagePullBackOff 0 12h
>>
>> kubernetes-dashboard
>> dashboard-metrics-scraper-5cb4f4bb9c-ljrh4 0/1
>> Pending 0 12h
>>
>> kubernetes-dashboard
>> kubernetes-dashboard-6967859bff-b9lm5 0/1
>> Pending 0 12h
>>
>> When i want to check the pods, it says that i need to be logged in to the
>> server
>>
>> skripsi@cloudstack:~$ kubectl describe pod weave-net-hcsql
>>
>> E1011 02:30:01.456779 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> E1011 02:30:01.457860 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> E1011 02:30:01.458810 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> E1011 02:30:01.460754 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> E1011 02:30:01.462716 23642 memcache.go:265] couldn't get current server
>> API group list: the server has asked for the client to provide credentials
>>
>> error: You must be logged in to the server (the server has asked for the
>> client to provide credentials)
>>
>> Can you please guide me what should i do. thank you :)
>>
>>
>>
>>
>>
>>
Re: Create Kubernetes Cluster Problem
Posted by Raihan Jana Prasetya <ra...@gmail.com>.
Hi Kiran,
Thank you for the respond. yes i have used the same command to generate the
ISO. Last night i turned off the server, and this morning i checked, all of
the pods are now running, but NOT READY yet. I think restart made them
running now.
The issue i'm facing now is, i'm trying to start the k8s cluster again from
the UI, but it's been 40 minutes on the "SCHEDULED" state on the "Events"
tab and the state of the cluster and on the Kubernetes tab the state of the
cluster is "Error". I've run this command too:
skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf create serviceaccount
dashboard-admin-sa
serviceaccount/dashboard-admin-sa created
skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf create
clusterrolebinding dashboard-admin-sa --clusterrole=cluster-admin
--serviceaccount=default:dashboard-admin-sa
clusterrolebinding.rbac.authorization.k8s.io/dashboard-admin-sa created
*creating token*
skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get nodes
--all-namespaces
NAME STATUS ROLES AGE VERSION
k8s-k8s-1272-control-18b19d3c77f Ready control-plane 37h v1.27.2
k8s-k8s-1272-node-18b19d40e2b Ready <none> 37h v1.27.2
skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
--all-namespaces
NAMESPACE NAME
READY STATUS RESTARTS AGE
kube-system coredns-5d78c9869d-ckm89
1/1 Running 1 (<invalid> ago) 37h
kube-system coredns-5d78c9869d-spn7x
1/1 Running 1 (<invalid> ago) 37h
kube-system etcd-k8s-k8s-1272-control-18b19d3c77f
0/1 Running 3 (<invalid> ago) 37h
kube-system kube-apiserver-k8s-k8s-1272-control-18b19d3c77f
0/1 Running 3 (<invalid> ago) 37h
kube-system
kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 0/1 Running
3 (<invalid> ago) 37h
kube-system kube-proxy-s9jv8
1/1 Running 3 (<invalid> ago) 37h
kube-system kube-proxy-zvml6
1/1 Running 3 (<invalid> ago) 37h
kube-system kube-scheduler-k8s-k8s-1272-control-18b19d3c77f
0/1 Running 3 (<invalid> ago) 37h
kube-system weave-net-hcsql
2/2 Running 3 (<invalid> ago) 37h
kube-system weave-net-xnq5k
2/2 Running 3 (<invalid> ago) 37h
kubernetes-dashboard dashboard-metrics-scraper-5cb4f4bb9c-ljrh4
1/1 Running 1 (<invalid> ago) 37h
kubernetes-dashboard kubernetes-dashboard-6967859bff-b9lm5
1/1 Running 1 (<invalid> ago) 37h
Regards,
Raihan
On Wed, Oct 11, 2023 at 6:06 PM Kiran Chavala <ki...@shapeblue.com>
wrote:
> Hi Raihan
>
> I was able to launch a working k8s cluster successfully after generating
> the iso for 1.2.7.2
>
> Please use the following command to generate the ISO
>
> ./create-kubernetes-binaries-iso.sh ./ 1.27.2 1.3.0 1.27.0
> https://raw.githubusercontent.com/weaveworks/weave/master/prog/weave-kube/weave-daemonset-k8s-1.11.yaml
> https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml
> setup-1.27.2<
> https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml%20setup-1.27.2
> >
>
> Regards
> Kiran
>
> From: Kiran Chavala <ki...@shapeblue.com>
> Date: Wednesday, 11 October 2023 at 3:32 PM
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Subject: Re: Create Kubernetes Cluster Problem
> Hi Raihan
>
>
> Could you use the community generated Kubernetes iso
>
> https://download.cloudstack.org/cks/setup-1.27.3.iso
>
>
> Meanwhile I will cross check with 1.27.2 version locally and let you know
> if I can reproduce the issue
>
> Regards
> Kiran
>
> From: Raihan Jana Prasetya <ra...@gmail.com>
> Date: Wednesday, 11 October 2023 at 8:30 AM
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Subject: Create Kubernetes Cluster Problem
> Hello,
>
> I have a problem when creating Kubernetes cluster on apache cloudstack
> version 1.18.1 with this Kubernetes version
> 1.27.2, kubernetes version, see
> https://github.com/kubernetes/kubernetes/releases
>
> 1.3.0, CNI version, see
> https://github.com/containernetworking/plugins/releases
>
> 1.27.0, cri-tools version, see
> https://github.com/kubernetes-sigs/cri-tools/releases
>
> 1.11, weave addon *for* kubernetes, see
> https://github.com/weaveworks/weave/tree/master/prog/weave-kube
>
> 2.7.0, kubernetes dashboard version, see
> https://github.com/kubernetes/dashboard/release
>
>
> the cluster always fails to start, but the control and regular nodes is
> running. This is the issue I found when I check the pods
>
> skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
> --all-namespaces
>
> NAMESPACE
> NAME READY
> STATUS RESTARTS AGE
>
> kube-system
> coredns-5d78c9869d-ckm89 0/1
> Pending 0 12h
>
> kube-system
> coredns-5d78c9869d-spn7x 0/1
> Pending 0 12h
>
> kube-system
> etcd-k8s-k8s-1272-control-18b19d3c77f 1/1
> Running 1 (32m ago) 12h
>
> kube-system
> kube-apiserver-k8s-k8s-1272-control-18b19d3c77f 1/1
> Running 1 (32m ago) 12h
>
> kube-system
> kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 1/1
> Running 1 (32m ago) 12h
>
> kube-system
> kube-proxy-s9jv8 1/1
> Running 1 (32m ago) 12h
>
> kube-system
> kube-proxy-zvml6 1/1
> Running 1 (32m ago) 12h
>
> kube-system
> kube-scheduler-k8s-k8s-1272-control-18b19d3c77f 1/1
> Running 1 (32m ago) 12h
>
> kube-system
> weave-net-hcsql 0/2
> Init:ImagePullBackOff 0 12h
>
> kube-system
> weave-net-xnq5k 0/2
> Init:ImagePullBackOff 0 12h
>
> kubernetes-dashboard
> dashboard-metrics-scraper-5cb4f4bb9c-ljrh4 0/1
> Pending 0 12h
>
> kubernetes-dashboard
> kubernetes-dashboard-6967859bff-b9lm5 0/1
> Pending 0 12h
>
> When i want to check the pods, it says that i need to be logged in to the
> server
>
> skripsi@cloudstack:~$ kubectl describe pod weave-net-hcsql
>
> E1011 02:30:01.456779 23642 memcache.go:265] couldn't get current server
> API group list: the server has asked for the client to provide credentials
>
> E1011 02:30:01.457860 23642 memcache.go:265] couldn't get current server
> API group list: the server has asked for the client to provide credentials
>
> E1011 02:30:01.458810 23642 memcache.go:265] couldn't get current server
> API group list: the server has asked for the client to provide credentials
>
> E1011 02:30:01.460754 23642 memcache.go:265] couldn't get current server
> API group list: the server has asked for the client to provide credentials
>
> E1011 02:30:01.462716 23642 memcache.go:265] couldn't get current server
> API group list: the server has asked for the client to provide credentials
>
> error: You must be logged in to the server (the server has asked for the
> client to provide credentials)
>
> Can you please guide me what should i do. thank you :)
>
>
>
>
>
>
Re: Create Kubernetes Cluster Problem
Posted by Kiran Chavala <ki...@shapeblue.com>.
Hi Raihan
I was able to launch a working k8s cluster successfully after generating the iso for 1.2.7.2
Please use the following command to generate the ISO
./create-kubernetes-binaries-iso.sh ./ 1.27.2 1.3.0 1.27.0 https://raw.githubusercontent.com/weaveworks/weave/master/prog/weave-kube/weave-daemonset-k8s-1.11.yaml https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml setup-1.27.2<https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml%20setup-1.27.2>
Regards
Kiran
From: Kiran Chavala <ki...@shapeblue.com>
Date: Wednesday, 11 October 2023 at 3:32 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Re: Create Kubernetes Cluster Problem
Hi Raihan
Could you use the community generated Kubernetes iso
https://download.cloudstack.org/cks/setup-1.27.3.iso
Meanwhile I will cross check with 1.27.2 version locally and let you know if I can reproduce the issue
Regards
Kiran
From: Raihan Jana Prasetya <ra...@gmail.com>
Date: Wednesday, 11 October 2023 at 8:30 AM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Create Kubernetes Cluster Problem
Hello,
I have a problem when creating Kubernetes cluster on apache cloudstack
version 1.18.1 with this Kubernetes version
1.27.2, kubernetes version, see
https://github.com/kubernetes/kubernetes/releases
1.3.0, CNI version, see https://github.com/containernetworking/plugins/releases
1.27.0, cri-tools version, see
https://github.com/kubernetes-sigs/cri-tools/releases
1.11, weave addon *for* kubernetes, see
https://github.com/weaveworks/weave/tree/master/prog/weave-kube
2.7.0, kubernetes dashboard version, see
https://github.com/kubernetes/dashboard/release
the cluster always fails to start, but the control and regular nodes is
running. This is the issue I found when I check the pods
skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
--all-namespaces
NAMESPACE
NAME READY
STATUS RESTARTS AGE
kube-system
coredns-5d78c9869d-ckm89 0/1
Pending 0 12h
kube-system
coredns-5d78c9869d-spn7x 0/1
Pending 0 12h
kube-system
etcd-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-apiserver-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-proxy-s9jv8 1/1
Running 1 (32m ago) 12h
kube-system
kube-proxy-zvml6 1/1
Running 1 (32m ago) 12h
kube-system
kube-scheduler-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
weave-net-hcsql 0/2
Init:ImagePullBackOff 0 12h
kube-system
weave-net-xnq5k 0/2
Init:ImagePullBackOff 0 12h
kubernetes-dashboard
dashboard-metrics-scraper-5cb4f4bb9c-ljrh4 0/1
Pending 0 12h
kubernetes-dashboard
kubernetes-dashboard-6967859bff-b9lm5 0/1
Pending 0 12h
When i want to check the pods, it says that i need to be logged in to the
server
skripsi@cloudstack:~$ kubectl describe pod weave-net-hcsql
E1011 02:30:01.456779 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.457860 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.458810 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.460754 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.462716 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
error: You must be logged in to the server (the server has asked for the
client to provide credentials)
Can you please guide me what should i do. thank you :)
Re: Create Kubernetes Cluster Problem
Posted by Kiran Chavala <ki...@shapeblue.com>.
Hi Raihan
Could you use the community generated Kubernetes iso
https://download.cloudstack.org/cks/setup-1.27.3.iso
Meanwhile I will cross check with 1.27.2 version locally and let you know if I can reproduce the issue
Regards
Kiran
From: Raihan Jana Prasetya <ra...@gmail.com>
Date: Wednesday, 11 October 2023 at 8:30 AM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Create Kubernetes Cluster Problem
Hello,
I have a problem when creating Kubernetes cluster on apache cloudstack
version 1.18.1 with this Kubernetes version
1.27.2, kubernetes version, see
https://github.com/kubernetes/kubernetes/releases
1.3.0, CNI version, see https://github.com/containernetworking/plugins/releases
1.27.0, cri-tools version, see
https://github.com/kubernetes-sigs/cri-tools/releases
1.11, weave addon *for* kubernetes, see
https://github.com/weaveworks/weave/tree/master/prog/weave-kube
2.7.0, kubernetes dashboard version, see
https://github.com/kubernetes/dashboard/release
the cluster always fails to start, but the control and regular nodes is
running. This is the issue I found when I check the pods
skripsi@cloudstack:~$ kubectl --kubeconfig kube.conf get pods
--all-namespaces
NAMESPACE
NAME READY
STATUS RESTARTS AGE
kube-system
coredns-5d78c9869d-ckm89 0/1
Pending 0 12h
kube-system
coredns-5d78c9869d-spn7x 0/1
Pending 0 12h
kube-system
etcd-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-apiserver-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-controller-manager-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
kube-proxy-s9jv8 1/1
Running 1 (32m ago) 12h
kube-system
kube-proxy-zvml6 1/1
Running 1 (32m ago) 12h
kube-system
kube-scheduler-k8s-k8s-1272-control-18b19d3c77f 1/1
Running 1 (32m ago) 12h
kube-system
weave-net-hcsql 0/2
Init:ImagePullBackOff 0 12h
kube-system
weave-net-xnq5k 0/2
Init:ImagePullBackOff 0 12h
kubernetes-dashboard
dashboard-metrics-scraper-5cb4f4bb9c-ljrh4 0/1
Pending 0 12h
kubernetes-dashboard
kubernetes-dashboard-6967859bff-b9lm5 0/1
Pending 0 12h
When i want to check the pods, it says that i need to be logged in to the
server
skripsi@cloudstack:~$ kubectl describe pod weave-net-hcsql
E1011 02:30:01.456779 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.457860 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.458810 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.460754 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
E1011 02:30:01.462716 23642 memcache.go:265] couldn't get current server
API group list: the server has asked for the client to provide credentials
error: You must be logged in to the server (the server has asked for the
client to provide credentials)
Can you please guide me what should i do. thank you :)