grey

pod-1 primary on node3,secondary on node 04, use followTopology + autoplace （or manual,we decide which node），When I'm done developing，can i bring up a PR

> It looks like you have a `cluster` label in one metric but not in the other. Does `container_cpu_usage_seconds_total{container!="POD",image!="",job="kubelet",metrics_path="/metrics/cadvisor", cluster!=""}` and `kube_pod_info{node!="",cluster!=""}` return any output? i did, return no data

> It looks like you have a `cluster` label in one metric but not in the other. Does `container_cpu_usage_seconds_total{container!="POD",image!="",job="kubelet",metrics_path="/metrics/cadvisor", cluster!=""}` and `kube_pod_info{node!="",cluster!=""}` return any output? kube_pod_info{node!="",cluster!=""} return many kube_pod_info{cluster="",container="kube-rbac-proxy-main",created_by_kind="",created_by_name="",host_ip="",instance="",job="kube-state-metrics",namespace="default",node="master01",pod="netshoot",pod_ip="",uid="ef6d61ac-fed4-4ee3-b757-de912a6863fb"}

container_cpu_usage_seconds_total{container!="POD",image!="",job="kubelet",metrics_path="/metrics/cadvisor", cluster!=""} return no data

> It seems that your cluster is not configured correctly and you have `cluster` label attached to metrics from kube-state-metrics, but not to metrics from kubelet. You need to have...

> 同样的需求，前端能不能加个context path呀，这样就能通过我们的nginx 配置location转发过来了

> @yangzehan您好，目前 master 分支已经支持按需构建工件。您可以尝试通过 master 分支自行构建 kk 二进制文件，或者等待即将发布的 v3.1.0-rc.1 版本。 目前发布了吗？同样有这个需求，部署完后，需要一些业务的镜像导入导出

问题非常好，我也遇到扩容的问题，还需要在原有的机器上去执行，但是原有的某台机器已经网卡有问题，ssh不上去了，这时候新扩容的机器也加不进去，束手无策

> ，我也遇到扩容的问题，还需要在原有的机器上去执行，但是原有的某台机器已经网卡有问题，ssh不上去了，这时候新扩容的机器也加不进去，束手无策 这种场景现在kk支持吗？

赞，最好能支持下离线环境，拓展市场的私有化部署