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
~]# kubectl get pod,svc -n monitoring | grep notif
pod/notification-manager-deployment-7bffdfc9f-f99jh 1/1 Running 0 34m
pod/notification-manager-operator-7cc9c59c75-fr759 2/2 Running 0 35m
service/notification-manager-controller-metrics ClusterIP 10.109.222.237 <none> 8443/TCP 35m
service/notification-manager-svc ClusterIP 10.107.83.81 <none> 19093/TCP 34m
service/notification-manager-webhook ClusterIP 10.110.101.226 <none> 443/TCP 35m
~]# kubectl apply -f receiver-global.yaml
Error from server (InternalError): error when creating "receiver-global.yaml": Internal error occurred: failed calling webhook "vreceiver.notification.kubesphere.io": failed to call webhook: Post "https://notification-manager-webhook.monitoring.svc:443/validate-notification-kubesphere-io-v2beta2-receiver?timeout=10s": x509: certificate is valid for notification-manager-webhook.kubesphere-monitoring-system.svc, not notification-manager-webhook.monitoring.svc
When deployed in other clusters, the following error will occur
Error from server (InternalError): error when creating "receiver-global.yaml": Internal error occurred: failed calling webhook "vreceiver.notification.kubesphere.io": failed to call webhook: Post "https://notification-manager-webhook.monitoring.svc:443/validate-notification-kubesphere-io-v2beta2-receiver?timeout=10s": x509: certificate is valid for notification-manager-webhook.kubesphere-monitoring-system.svc, not notification-manager-webhook.monitoring.svc
The text was updated successfully, but these errors were encountered:
DesistDaydream
changed the title
Certificate issues prevent Receivers from being created in other namespaces
Receiver is not recognized by NMs deployed in other namespaces because certificate issues
May 13, 2022
Is the certificate used by NM here?
When deployed in other clusters, the following error will occur
The text was updated successfully, but these errors were encountered: