kubernetes: 【An error occurred attempting to install kubernetes learning】
🏄♂️ demand
I’m hoping to learn kuberntes and become a community contributor, and I’m hoping someone can help me solve some problems
⚡ Description of the Problem
branch:
root@cubmaster01:~/go/src/k8s.io/kubernetes# git branch
* kube1.24
master
ubuntu20.04:
Linux cubmaster01 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
build errors:
root@cubmaster01:~/go/src/k8s.io/kubernetes# sudo ./hack/local-up-cluster.sh
make: Entering directory '/root/go/src/k8s.io/kubernetes'
make[1]: Entering directory '/root/go/src/k8s.io/kubernetes'
+++ [1201 03:25:54] Building go targets for linux/amd64
k8s.io/kubernetes/hack/make-rules/helpers/go2make (non-static)
make[1]: Leaving directory '/root/go/src/k8s.io/kubernetes'
+++ [1201 03:27:05] Building go targets for linux/amd64
k8s.io/kubernetes/cmd/kubectl (static)
k8s.io/kubernetes/cmd/kube-apiserver (static)
k8s.io/kubernetes/cmd/kube-controller-manager (static)
k8s.io/kubernetes/cmd/cloud-controller-manager (non-static)
k8s.io/kubernetes/cmd/kubelet (non-static)
k8s.io/kubernetes/cmd/kube-proxy (static)
k8s.io/kubernetes/cmd/kube-scheduler (static)
make: Leaving directory '/root/go/src/k8s.io/kubernetes'
API SERVER secure port is free, proceeding...
Detected host and ready to start services. Doing some housekeeping first...
Using GO_OUT /root/go/src/k8s.io/kubernetes/_output/local/bin/linux/amd64
Starting services now!
Starting etcd
etcd --advertise-client-urls http://127.0.0.1:2379 --data-dir /tmp/tmp.her0ePjrKp --listen-client-urls http://127.0.0.1:2379 --log-level=warn 2> "/tmp/etcd.log" >/dev/null
Waiting for etcd to come up.
+++ [1201 03:28:16] On try 2, etcd: : {"health":"true","reason":""}
{"header":{"cluster_id":"14841639068965178418","member_id":"10276657743932975437","revision":"2","raft_term":"2"}}Generating a RSA private key
........+++++
.........................................................................................................................+++++
writing new private key to '/var/run/kubernetes/server-ca.key'
-----
Generating a RSA private key
.........................+++++
.................................+++++
writing new private key to '/var/run/kubernetes/client-ca.key'
-----
Generating a RSA private key
.........................................................+++++
................................+++++
writing new private key to '/var/run/kubernetes/request-header-ca.key'
-----
2022/12/01 03:28:17 [INFO] generate received request
2022/12/01 03:28:17 [INFO] received CSR
2022/12/01 03:28:17 [INFO] generating key: rsa-2048
2022/12/01 03:28:17 [INFO] encoded CSR
2022/12/01 03:28:17 [INFO] signed certificate with serial number 131182041241690291571408941114978154868705861579
2022/12/01 03:28:17 [INFO] generate received request
2022/12/01 03:28:17 [INFO] received CSR
2022/12/01 03:28:17 [INFO] generating key: rsa-2048
2022/12/01 03:28:17 [INFO] encoded CSR
2022/12/01 03:28:17 [INFO] signed certificate with serial number 467109587719679993853631126723843205268303578178
2022/12/01 03:28:17 [INFO] generate received request
2022/12/01 03:28:17 [INFO] received CSR
2022/12/01 03:28:17 [INFO] generating key: rsa-2048
2022/12/01 03:28:17 [INFO] encoded CSR
2022/12/01 03:28:17 [INFO] signed certificate with serial number 56026979915374047994065025399275609826564835988
2022/12/01 03:28:17 [INFO] generate received request
2022/12/01 03:28:17 [INFO] received CSR
2022/12/01 03:28:17 [INFO] generating key: rsa-2048
2022/12/01 03:28:18 [INFO] encoded CSR
2022/12/01 03:28:18 [INFO] signed certificate with serial number 408706275885850925762903367258359186972619427529
2022/12/01 03:28:18 [INFO] generate received request
2022/12/01 03:28:18 [INFO] received CSR
2022/12/01 03:28:18 [INFO] generating key: rsa-2048
2022/12/01 03:28:18 [INFO] encoded CSR
2022/12/01 03:28:18 [INFO] signed certificate with serial number 414443017327089315447535639883176570269157285457
2022/12/01 03:28:18 [INFO] generate received request
2022/12/01 03:28:18 [INFO] received CSR
2022/12/01 03:28:18 [INFO] generating key: rsa-2048
2022/12/01 03:28:18 [INFO] encoded CSR
2022/12/01 03:28:18 [INFO] signed certificate with serial number 359674450042553518135715955939967912680856096990
2022/12/01 03:28:18 [INFO] generate received request
2022/12/01 03:28:18 [INFO] received CSR
2022/12/01 03:28:18 [INFO] generating key: rsa-2048
2022/12/01 03:28:18 [INFO] encoded CSR
2022/12/01 03:28:18 [INFO] signed certificate with serial number 227812532356544646036907333725398460340472761540
2022/12/01 03:28:18 [INFO] generate received request
2022/12/01 03:28:18 [INFO] received CSR
2022/12/01 03:28:18 [INFO] generating key: rsa-2048
2022/12/01 03:28:18 [INFO] encoded CSR
2022/12/01 03:28:18 [INFO] signed certificate with serial number 456216072297913140921208077503472773302612365418
Waiting for apiserver to come up
+++ [1201 03:28:25] On try 6, apiserver: : ok
clusterrolebinding.rbac.authorization.k8s.io/kube-apiserver-kubelet-admin created
clusterrolebinding.rbac.authorization.k8s.io/kubelet-csr created
Cluster "local-up-cluster" set.
use 'kubectl --kubeconfig=/var/run/kubernetes/admin-kube-aggregator.kubeconfig' to use the aggregated API server
serviceaccount/coredns created
clusterrole.rbac.authorization.k8s.io/system:coredns created
clusterrolebinding.rbac.authorization.k8s.io/system:coredns created
configmap/coredns created
deployment.apps/coredns created
service/kube-dns created
coredns addon successfully deployed.
Checking CNI Installation at /opt/cni/bin
CNI Installation not found at /opt/cni/bin
Installing CNI plugin binaries ...
curl: (18) transfer closed with 27223798 bytes remaining to read
Configuring cni
{
"cniVersion": "0.4.0",
"name": "containerd-net",
"plugins": [
{
"type": "bridge",
"bridge": "cni0",
"isGateway": true,
"ipMasq": true,
"promiscMode": true,
"ipam": {
"type": "host-local",
"ranges": [
[{
"subnet": "10.88.0.0/16"
}],
[{
"subnet": "2001:4860:4860::/64"
}]
],
"routes": [
{ "dst": "0.0.0.0/0" },
{ "dst": "::/0" }
]
}
},
{
"type": "portmap",
"capabilities": {"portMappings": true}
}
]
}
WARNING : The kubelet is configured to not fail even if swap is enabled; production deployments should disable swap unless testing NodeSwap feature.
2022/12/01 03:37:44 [INFO] generate received request
2022/12/01 03:37:44 [INFO] received CSR
2022/12/01 03:37:44 [INFO] generating key: rsa-2048
2022/12/01 03:37:44 [INFO] encoded CSR
2022/12/01 03:37:44 [INFO] signed certificate with serial number 301766963461269587005666474264450659770301170778
kubelet ( 225612 ) is running.
wait kubelet ready
No resources found
No resources found
No resources found
No resources found
No resources found
No resources found
No resources found
127.0.0.1 NotReady <none> 2s v1.24.0-dirty
2022/12/01 03:38:00 [INFO] generate received request
2022/12/01 03:38:00 [INFO] received CSR
2022/12/01 03:38:00 [INFO] generating key: rsa-2048
2022/12/01 03:38:00 [INFO] encoded CSR
2022/12/01 03:38:00 [INFO] signed certificate with serial number 524544021140729048983087145058852517235221351025
Create default storage class for
storageclass.storage.k8s.io/standard created
Local Kubernetes cluster is running. Press Ctrl-C to shut it down.
Logs:
/tmp/kube-apiserver.log
/tmp/kube-controller-manager.log
/tmp/kube-proxy.log
/tmp/kube-scheduler.log
/tmp/kubelet.log
To start using your cluster, you can open up another terminal/tab and run:
export KUBECONFIG=/var/run/kubernetes/admin.kubeconfig
cluster/kubectl.sh
Alternatively, you can write to the default kubeconfig:
export KUBERNETES_PROVIDER=local
cluster/kubectl.sh config set-cluster local --server=https://localhost:6443 --certificate-authority=/var/run/kubernetes/server-ca.crt
cluster/kubectl.sh config set-credentials myself --client-key=/var/run/kubernetes/client-admin.key --client-certificate=/var/run/kubernetes/client-admin.crt
cluster/kubectl.sh config set-context local --cluster=local --user=myself
cluster/kubectl.sh config use-context local
cluster/kubectl.sh
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (11 by maintainers)
I’m sorry, I don’t actively use this tool, I maintain and recommend KIND for this purpose https://sigs.k8s.io/kind
I think you’ll find it easier to work with
yep
hi, we have support channels for that purpose. please try asking there https://github.com/kubernetes/kubernetes/blob/master/SUPPORT.md
/close