Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receiver is not recognized by NMs deployed in other namespaces because certificate issues #144

Open
DesistDaydream opened this issue May 13, 2022 · 0 comments

Comments

@DesistDaydream
Copy link

DesistDaydream commented May 13, 2022

Is the certificate used by NM here?

image

~]# 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
@DesistDaydream 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant