erda-project / kubeprober Goto Github PK

What happened:

standalone案例无法正确运行，现象：

1. probe-agent启动报错找不到configmap-probeagent
2. probe-agent日志报错各类资源list等权限forbidden
3. Prober 示例运行job提示无法找到configmap-extra-config

What you expected to happen:

standalone案例正确运行

How to reproduce it (as minimally and precisely as possible):

1. 按照文档 https://docs.erda.cloud/1.5/manual/eco-tools/kubeprober/best-practices/standalone_kubeprober.html 进行操作，prober-agent容器无法正常启动；
2. 按照文档 https://docs.erda.cloud/1.5/manual/eco-tools/kubeprober/guides/first_prober.html 运行prober示例无法正确运行job

Anything else we need to know?:

已自行定位问题原因并修改：
dotDuck@ade3b0d#diff-ebef744877d88253a7e2a26f413155959097fe3659045131b32418fb9af80937
如果可以的话可以进行pull-request。

问题1原因：probe-agent-standalone.yaml声明问题

• 缺少configmapprobeagent的声明（对应现象1）
• serviceaccountkubeprober-worker声明后未使用，应该将kubeprober-worker-rolebinding绑定的serviceacccount更换为kubeprober（对应现象2）
• probe-agent镜像更新到docker-hub中最新版（也可忽略）
• 仍有其他configmap找不到的日志报错，但是不影响整体运行，如：dice-cluster-info、dice-tools-info、dice-addon-info

问题2原因：prober-demo-example声明问题

• 缺少configmapextra-config的声明，但是配置内容无从参考，也找不到合适的新增位置，临时新建cm解决（对应现象3）

Environment:

• Erda version: 无
• Kubernetes version (use kubectl version): Kind kubernetes v1.19.11

Hi, I found the project has not release for a long time, had the project been stopped? I think that is a nice project and should be go on .

probe yaml

apiVersion: kubeprober.erda.cloud/v1
kind: Probe
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"kubeprober.erda.cloud/v1","kind":"Probe","metadata":{"annotations":{},"name":"probe-test01","namespace":"kubeprober"},"spec":{"probeList":[{"name":"probe-test01","spec":{"containers":[{"image":"kubeprober/demo-error:v0.0.1","name":"demo-error","resources":{"requests":{"cpu":"10m","memory":"50Mi"}}}],"restartPolicy":"Never"}}]}}
creationTimestamp: "2021-08-18T09:24:26Z"
generation: 1
name: probe-test01
namespace: kubeprober
resourceVersion: "1255475"
selfLink: /apis/kubeprober.erda.cloud/v1/namespaces/kubeprober/probes/probe-test01
uid: 1c6a2f23-a68c-4283-9869-0c2ed3e891c7
spec:
policy: {}
probeList:

• name: probe-test01
  spec:
  containers:
  • image: kubeprober/demo-error:v0.0.1
    name: demo-error
    resources:
    requests:
    cpu: 10m
    memory: 50Mi
    restartPolicy: Never
    status:
    md5: 0e69f266c6e6d360c7e4130a4b4e6ff4

probe-agent error

What happened:

web hook svc was deleted accidentally while excuting agent's undeploy

How to reproduce it (as minimally and precisely as possible):

install master and agent according to the install doc,then execute APP=probe-agent make undeploy

Environment:

• Erda version: master branch code
• Kubernetes version (use kubectl version): 1.19.11
• OS (e.g: cat /etc/os-release): mac os

What would you like to be added:

Does kubeprober support k8s 1.14 ? In k8s 1.14,we don't have 'v1' version.

根据该教程创建alert失败
错误信息:
error: unable to recognize "alert.yaml": no matches for kind "Alert" in version "kubeprober.erda.cloud/v1"

I have deployed a test case, but i can‘t get the probestatus。

➜ samples git:(master) ✗ kubectl get cluster
NAME VERSION NODECOUNT PROBENAMESPACES HEARTBEATTIME SECRETKEY PROBE AGE
moon v1.19.0 1 kubeprober 2021-08-18 08:53:25 4012ecac-08a3-4a6c-a206-b9447a13d987 33m
➜ samples git:(master) ✗
➜ samples git:(master) ✗
➜ samples git:(master) ✗ kubectl get probe
NAME RUNINTERVAL AGE
probe-cron-link-test 2 19m
probe-link-test 13m
probe-link-test1 2m47s
➜ samples git:(master) ✗ kubectl get probestatus -A
No resources found
➜ samples git:(master) ✗
➜ samples git:(master) ✗
➜ samples git:(master) ✗ kubectl get cluster --show-labels
NAME VERSION NODECOUNT PROBENAMESPACES HEARTBEATTIME SECRETKEY PROBE AGE LABELS
moon v1.19.0 1 kubeprober 2021-08-18 08:53:50 4012ecac-08a3-4a6c-a206-b9447a13d987 33m probe/probe-cron-link-test=true,probe/probe-cron-sample=true,probe/probe-link-test1=true,probe/probe-link-test=true
➜ samples git:(master) ✗

关于诊断的结果实现可视化没有在项目的相关文档中体现出来，

以及如何对接到prometheus 配置以及暴露的metrics 都有哪些文档中没有相关的描述 ，是否可以完善文档或者补全相关可视化操作或功能，谢谢。

What would you like to be added:

Why is this needed: