KubeSphere 3.0 相关信息

rayzhou2017

rysinal 人多，等等，会联系你的

wangpo1991

估计是我的网不好，我在dockerhub上搜了一把果然有，我手动在节点上拉一下，拉下来了

wangpo1991

按照install去安装为啥没有提示前提需要安装，但是这安装的时候却报错了，挂载卷的问题
Name: redis-644bc597b9-h6sbr
Namespace: kubesphere-system
Priority: 0
Node: <none>
Labels: app=redis
pod-template-hash=644bc597b9
tier=database
version=redis-4.0
Annotations: <none>
Status: Pending
IP:

IPs: <none>
Controlled By: ReplicaSet/redis-644bc597b9
Containers:
redis:
Image: redis:5.0.5-alpine
Port: 6379/TCP
Host Port: 0/TCP
Limits:
cpu: 1
memory: 1000Mi
Requests:
cpu: 20m
memory: 100Mi
Environment: <none>
Mounts:
/data from redis-pvc (rw,path=“redis-data”)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-cssgb (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
redis-pvc:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: redis-pvc
ReadOnly: false
default-token-cssgb:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-cssgb
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: CriticalAddonsOnly
node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message

Warning FailedScheduling <unknown> default-scheduler Failed to bind volumes: timed out waiting for the condition
Warning FailedScheduling <unknown> default-scheduler Failed to bind volumes: timed out waiting for the condition
Warning FailedScheduling <unknown> default-scheduler Failed to bind volumes: timed out waiting for the condition
Warning FailedScheduling <unknown> default-scheduler Failed to bind volumes: timed out waiting for the condition

rayzhou2017

wangpo1991 你可以到kubekey下提一个issue

Feynman

rysinal 这两天会联系你的

wangtao131520

Feynman 麻烦帮忙看一下，这个问题怎么解决呢 https://kubesphere.com.cn/forum/d/2320-apiservermoinitoring-service-address-in-configration-must-not-be-empty

wangpo1991

感觉我距离胜利就差一只脚了

wangpo1991

rayzhou2017 嗯，好滴

wangpo1991

rayzhou2017 忘了，我是按照在K8S基础之上安装的，不是上面那个kubeKey

rayzhou2017

wangpo1991 在已有K8s上装3.0参考这个文档 https://github.com/kubesphere/ks-installer/blob/v3.0.0-alpha.1/docs/InstallGuide.md。有前提条件说明。

wangpo1991

我好像漏了一步，我去试一下，默认卷不太对

zoey

安装完成后，在服务组件那里看都是健康的，但是在点击告警策略时报Internal Server Error，查看报警命名空间，有以下四个应用READY还是0

然后打算重新触发下告警系统的安装，结果提示 “ks-installer” not found，但我看ks-installer是在运行的，请问怎么处理？

Feynman

zoey Bug 请用英文提交到 GitHub issue，描述清楚如何复现。 3.0 没有用 configmap 来管理可插拔组件，请仔细阅读 Readme。

zoey

Feynman 🤣 哦哦好的。

tscswcn

root@cd2 kubesphere]# ./kk create cluster
+-------------+------+------+---------+----------+-------+-------+-----------+--------+------------+-------------+------------------+--------------+
| name        | sudo | curl | openssl | ebtables | socat | ipset | conntrack | docker | nfs client | ceph client | glusterfs client |
time
  |
+-------------+------+------+---------+----------+-------+-------+-----------+--------+------------+-------------+------------------+--------------+
| ks-allinone | y    | y    | y       | y        |       | y     |           | y      | y          |             |                  |
CST 16:43:34 |
+-------------+------+------+---------+----------+-------+-------+-----------+--------+------------+-------------+------------------+--------------+

This is a simple check of your environment.
Before installation, you should ensure that your machines meet all requirements specified at
https://github.com/kubesphere/kubekey#requirements-and-recommendations

Continue this installation? [yes/no]: yes
INFO[16:43:37 CST] Downloading Installation Files
INFO[16:43:37 CST] Downloading kubeadm ...
INFO[16:43:37 CST] Downloading kubelet ...
INFO[16:43:37 CST] Downloading kubectl ...
INFO[16:43:37 CST] Downloading kubecni ...
INFO[16:43:37 CST] Downloading helm ...
INFO[16:43:38 CST] Configurating operating system ...
[ks-allinone 192.168.31.179] MSG:
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-arptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_local_reserved_ports = 30000-32767
INFO[16:43:38 CST] Installing docker ...
INFO[16:43:39 CST] Start to download images on all nodes
[ks-allinone] Downloading image: kubesphere/etcd:v3.3.12
[ks-allinone] Downloading image: kubesphere/pause:3.1
[ks-allinone] Downloading image: kubesphere/kube-apiserver:v1.17.8
[ks-allinone] Downloading image: kubesphere/kube-controller-manager:v1.17.8
[ks-allinone] Downloading image: kubesphere/kube-scheduler:v1.17.8
[ks-allinone] Downloading image: kubesphere/kube-proxy:v1.17.8
[ks-allinone] Downloading image: coredns/coredns:1.6.0
[ks-allinone] Downloading image: kubesphere/k8s-dns-node-cache:1.15.12
[ks-allinone] Downloading image: calico/kube-controllers:v3.14.1
[ks-allinone] Downloading image: calico/cni:v3.14.1
[ks-allinone] Downloading image: calico/node:v3.14.1
[ks-allinone] Downloading image: calico/pod2daemon-flexvol:v3.14.1
INFO[16:52:00 CST] Generating etcd certs
INFO[16:52:01 CST] Synchronizing etcd certs
INFO[16:52:01 CST] Creating etcd service
INFO[16:52:04 CST] Starting etcd cluster
[ks-allinone 192.168.31.179] MSG:
Configuration file already exists
Waiting for etcd to start
INFO[16:52:12 CST] Refreshing etcd configuration
INFO[16:52:12 CST] Get cluster status
[ks-allinone 192.168.31.179] MSG:
Cluster already exists.
[ks-allinone 192.168.31.179] MSG:
v1.17.8
[ks-allinone 192.168.31.179] Retrying ...
[ks-allinone 192.168.31.179] Retrying ...
[ks-allinone 192.168.31.179] Retrying ...
[ks-allinone 192.168.31.179] Retrying ...
[ks-allinone 192.168.31.179] Retrying ...
WARN[17:01:13 CST] Task failed ...
WARN[17:01:13 CST] error: Failed to upload kubeadm certs: Failed to exec command: sudo -E /bin/sh -c "/usr/local/bin/kubeadm init phase
upload-certs --upload-certs"
W0706 16:59:53.612803   14625 version.go:101] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://storage.googleapis.com/kubernetes-release/release/stable-1.txt: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
W0706 16:59:53.613601   14625 version.go:102] falling back to the local client version: v1.17.8
W0706 16:59:53.613775   14625 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0706 16:59:53.613785   14625 validation.go:28] Cannot validate kubelet config - no validator is available
[upload-certs] Storing the certificates in Secret "kubeadm-certs" in the "kube-system" Namespace
error execution phase upload-certs: error uploading certs: error creating token: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher: Process exited with status 1
Error: Failed to get cluster status: Failed to upload kubeadm certs: Failed to exec command: sudo -E /bin/sh -c "/usr/local/bin/kubeadm
init phase upload-certs --upload-certs"
W0706 16:59:53.612803   14625 version.go:101] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://storage.googleapis.com/kubernetes-release/release/stable-1.txt: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
W0706 16:59:53.613601   14625 version.go:102] falling back to the local client version: v1.17.8
W0706 16:59:53.613775   14625 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0706 16:59:53.613785   14625 validation.go:28] Cannot validate kubelet config - no validator is available
[upload-certs] Storing the certificates in Secret "kubeadm-certs" in the "kube-system" Namespace
error execution phase upload-certs: error uploading certs: error creating token: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher: Process exited with status 1
Usage:
  kk create cluster [flags]

Flags:
  -f, --file string              Path to a configuration file
  -h, --help                     help for cluster
      --with-kubernetes string   Specify a supported version of kubernetes (default "v1.17.8")
      --with-kubesphere          Deploy a specific version of kubesphere (default v3.0.0)

Global Flags:
      --debug   Print detailed information (default true)

Failed to get cluster status: Failed to upload kubeadm certs: Failed to exec command: sudo -E /bin/sh -c "/usr/local/bin/kubeadm init phase upload-certs --upload-certs"
W0706 16:59:53.612803   14625 version.go:101] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://storage.googleapis.com/kubernetes-release/release/stable-1.txt: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
W0706 16:59:53.613601   14625 version.go:102] falling back to the local client version: v1.17.8
W0706 16:59:53.613775   14625 validation.go:28] Cannot validate kube-proxy config - no validator is available
W0706 16:59:53.613785   14625 validation.go:28] Cannot validate kubelet config - no validator is available
[upload-certs] Storing the certificates in Secret "kubeadm-certs" in the "kube-system" Namespace
error execution phase upload-certs: error uploading certs: error creating token: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher: Process exited with status 1

tscswcn

tscswcn 没人帮着看？？

rayzhou2017

tscswcn 这个抛错很奇怪，怎么会访问 https://storage.googleapis.com/kubernetes-release/release/stable-1.txt:？ @Cauchy

Jeff

rayzhou2017 那个是kubeadm默认获取当前stable version kubernetes的地址

tscswcn

奥，但是毕竟是实际报错报出来的

Jeff

tscswcn socat 和 conntrack 没有安装？

tdcare

通过界面不能修改用户密码：

ks-apiserver：报如下错误
0708 15:54:00.293150 1 authentication.go:47] Unable to authenticate the request due to error: token is expired by 8h9m4s

E0708 15:54:02.000002 1 authentication.go:47] Unable to authenticate the request due to error: token is expired by 8h9m5s

E0708 15:54:28.801644 1 handler.go:489] the name of the object () does not match the name on the URL (tzw)

E0708 15:54:28.801742 1 utils.go:35] /go/src/kubesphere.io/kubesphere/pkg/kapis/iam/v1alpha2/handler.go:490 the name of the object () does not match the name on the URL (tzw)