After enabling the addon on AWS, the service seems to be stuck:
kubectl logs prometheus-operator-84c6fd4988-khdld -n monitoring
E1003 02:41:03.161196 1 reflector.go:134] github.com/coreos/prometheus-operator/pkg/prometheus/operator.go:399: Failed to list *v1beta2.StatefulSet: the server could not find the requested resource
E1003 02:41:03.161982 1 reflector.go:134] github.com/coreos/prometheus-operator/pkg/alertmanager/operator.go:233: Failed to list *v1beta2.StatefulSet: the server could not find the requested resource
E1003 02:41:04.162201 1 reflector.go:134] github.com/coreos/prometheus-operator/pkg/prometheus/operator.go:399: Failed to list *v1beta2.StatefulSet: the server could not find the requested resource
E1003 02:41:04.163077 1 reflector.go:134] github.com/coreos/prometheus-operator/pkg/alertmanager/operator.go:233: Failed to list *v1beta2.StatefulSet: the server could not find the requested resource
E1003 02:41:05.163200 1 reflector.go:134] github.com/coreos/prometheus-operator/pkg/prometheus/operator.go:399: Failed to list *v1beta2.StatefulSet: the server could not find the requested resource
E1003 02:41:05.164053 1 reflector.go:134] github.com/coreos/prometheus-operator/pkg/alertmanager/operator.go:233: Failed to list *v1beta2.StatefulSet: the server could not find the requested resource
E1003 02:41:06.164138 1 reflector.go:134] github.com/coreos/prometheus-operator/pkg/prometheus/operator.go:399: Failed to list *v1beta2.StatefulSet: the server could not find the requested resource
E1003 02:41:06.165006 1 reflector.go:134] github.com/coreos/prometheus-operator/pkg/alertmanager/operator.go:233: Failed to list *v1beta2.StatefulSet: the server could not find the requested resource
kubectl logs prometheus-adapter-66d74c78bd-r24cd -n monitoring
W1003 02:42:03.593889 1 x509.go:172] x509: subject with cn=127.0.0.1 is not in the allowed list: [front-proxy-client]
W1003 02:42:17.373496 1 x509.go:172] x509: subject with cn=127.0.0.1 is not in the allowed list: [front-proxy-client]
W1003 02:42:23.322337 1 x509.go:172] x509: subject with cn=127.0.0.1 is not in the allowed list: [front-proxy-client]
W1003 02:42:32.591538 1 x509.go:172] x509: subject with cn=127.0.0.1 is not in the allowed list: [front-proxy-client]
W1003 02:42:32.595793 1 x509.go:172] x509: subject with cn=127.0.0.1 is not in the allowed list: [front-proxy-client]
W1003 02:42:32.596412 1 x509.go:172] x509: subject with cn=127.0.0.1 is not in the allowed list: [front-proxy-client]
W1003 02:42:32.596872 1 x509.go:172] x509: subject with cn=127.0.0.1 is not in the allowed list: [front-proxy-client]
W1003 02:42:32.597339 1 x509.go:172] x509: subject with cn=127.0.0.1 is not in the allowed list: [front-proxy-client]
Does anyone has an idea on what would cause this?