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
Hi, i've found out, that, if you use an other namespace as default for setting up your applications and deploy the PodMonitoring Resource on it, the secret injection for the certification authority is not working.
i got following Error when apply PodMonitoring resource with terraform:
I am using an autopilot cluster.
│ Error: API response status: Failure
│
│ with module.vault-primary.kubernetes_manifest.metrics_monitoring,
│ on ../../modules/vault/monitoring.tf line 41, in resource "kubernetes_manifest" "metrics_monitoring":
│ 41: resource "kubernetes_manifest" "metrics_monitoring" {
│
│ admission webhook "validate.podmonitorings.gmp-operator.gke-gmp-system.monitoring.googleapis.com" denied the request: invalid definition for endpoint with index 0:
│ unable to parse or invalid Prometheus HTTP client config: must use namespace "example", got: "default"
To reproduce, just add you application and PodMonitoring to another namespace then default. I did the following:
create a secret with cluster root cert inside:
I believe this issue was reported already here #776 (comment) (not an issue that's why hard to find) and fixed e.g. #1007 in the recent versions of GMP (I think from 0.12).
Do you mind upgrading and checking? It was an GMP operator binary bug essentially.
I will close, but if I missed something or maybe it still does not work for you on the newer GMP version, we can reopen!
Hi, i've found out, that, if you use an other namespace as default for setting up your applications and deploy the PodMonitoring Resource on it, the secret injection for the certification authority is not working.
i got following Error when apply PodMonitoring resource with terraform:
I am using an autopilot cluster.
To reproduce, just add you application and PodMonitoring to another namespace then default. I did the following:
create a secret with cluster root cert inside:
add the role to for the secret usage:
and the role binding:
and finally the podMonitoring:
any suggestions how to fix this? If delete the ca part from tls and add
insecureSkipVerify: true
everything is working. If i deploy the example from this page (https://cloud.google.com/stackdriver/docs/managed-prometheus/setup-managed) on default namespace its also working.I think the namespace mentioned in the docs: https://github.com/GoogleCloudPlatform/prometheus-engine/blob/main/doc/api.md#monitoring.googleapis.com/v1.SecretKeySelector for SecretKeySelector is not working as expected.
The text was updated successfully, but these errors were encountered: