prometheus-community / prometheus-community/PushProx
Getting errors regarding "component" and "CRDs" when trying to install PushProxy with helm chart
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 811
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
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!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Helm chart templates and Values.yaml, then compare the cluster's available APIs with the reported policy/v1beta1 PodSecurityPolicy and monitoring.coreos.com/v1 ServiceMonitor resources. Check which chart resources require those APIs and document the required compatibility or installation steps; done means the reported install errors are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100