houshym

Results 8 comments of houshym

same on my side and I inform maintainers in the slack channel. I correct the selector but after I correct the selector I got 404 error. my problem with ingress...

Would you please update v1 to v2 in the operator hub? V2 is recommended, but it is not updated in the operator hub

same issue and I ran kubectl sniff prometheus-rancher-monitoring-prometheus-0 -n cattle-monitoring-system --privileged --socket /run/k3s/containerd/containerd.sock. but I got the following error ``` set -ex export CONTAINERD_SOCKET="/run/k3s/containerd/containerd.sock" export CONTAINERD_NAMESPACE="k8s.io" export CONTAINER_RUNTIME_ENDPOINT="unix:///host${CONTAINERD_SOCKET}" export IMAGE_SERVICE_ENDPOINT=${CONTAINER_RUNTIME_ENDPOINT}...

@cmdjulian any clue? I tried that one and it does not work.

Unfortunately I cannot run it. Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T16:31:21Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4+k3s1", GitCommit:"3e250fdbab72d88f7e6aae57446023a0567ffc97", GitTreeState:"clean", BuildDate:"2021-08-19T19:09:53Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} INFO[0000] waiting for...

I have same issue but in Rancher provisioned cluster