prometheus-community / PushProx

Proxy to allow Prometheus to scrape through NAT etc.
Apache License 2.0
719 stars 133 forks source link

Getting errors regarding "component" and "CRDs" when trying to install PushProxy with helm chart #161

Open moovs opened 10 months ago

moovs commented 10 months ago

Hi, I have tried to install pushproxy to my k8s cluster wiht helm chart but I received couple of errors: Error: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "pushprox-etcd-client" namespace: "prom-proxy" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first, resource mapping not found for name: "pushprox-etcd-proxy" namespace: "prom-proxy" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first, resource mapping not found for name: "prom-proxy-etcd" namespace: "prom-proxy" from "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1" ensure CRDs are installed first]

I was changing component in Values.yaml to kube-proxy, etcd and others but received below error.

Also I received CRDs errors.. Which CDRs I should install before isntalling helm chart?

Thanks!

ashishgupta-in commented 9 months ago

It seems you are using Kubernetes version which is >= 1.25. The error is corresponding to "PodSecurityPolicy" in version "policy/v1beta" of CRD. It has been removed in K8s version 1.25 as mentioned in their documentation.

Link for reference: K8s Pod Security Policy Documentation

You should follow step mentioned under this repository documentation by cloning the repo and installing the components instead of using 3rd party helm charts.

You can also create your own helm charts with a script defined in your pod initialization step for installation of push proxy components.

@SuperQ Let us know your thoughts on this.