You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My goal was to add a ingress config and some custom grafana environment variables.
Starting the deplyoment with kubectl apply --kustomize ../monitoring/
Did not work and I got the following output
...
.....
......
apiservice.apiregistration.k8s.io/v1beta1.metrics.k8s.io created
daemonset.apps/node-exporter created
ingress.networking.k8s.io/grafana created
unable to recognize "management/monitoring/": no matches for kind "Alertmanager" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "management/monitoring/": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
I guess the reason for that is that - as explained in the quick-start guide - I first need to
# 1st create setup manifests..
$ kubectl apply -f manifests/setup
# wait a little bit for system monitors...
$ until kubectl get servicemonitors --all-namespaces ; do date; sleep 1; echo ""; done
# create main manifests....
$ kubectl apply -f manifests/
After doing this, I can of course run my kustzomize script without errors and the exptected result:
kubectl apply --kustomize ../monitoring/
So I would not say this is a bug of kube-prometheus, but I ask if there is any way to solve this kind of setup using kustzomze in a better way?
The text was updated successfully, but these errors were encountered:
@rsoika - unfortunately there is not much this project can do to solve the issue. If you were to run kubectl apply --kustomize ../monitoring/ in a loop it will likely work once the api server has recognised the CRD's
What happened?
I tried to use the kustomization.yaml file to setup kube-prometheus.
For that I created my own kustomization file like this one:
My goal was to add a ingress config and some custom grafana environment variables.
Starting the deplyoment with
kubectl apply --kustomize ../monitoring/
Did not work and I got the following output
I guess the reason for that is that - as explained in the quick-start guide - I first need to
After doing this, I can of course run my kustzomize script without errors and the exptected result:
kubectl apply --kustomize ../monitoring/
So I would not say this is a bug of kube-prometheus, but I ask if there is any way to solve this kind of setup using kustzomze in a better way?
The text was updated successfully, but these errors were encountered: