# ERROR setup failed to register multicluster service {"error": "get api groups and resources:

**URL:** <https://forums.percona.com/t/error-setup-failed-to-register-multicluster-service-error-get-api-groups-and-resources/39048>\
**Category:** Percona Operator for MongoDB\
**Tags:** percona\
**Created:** [August 9, 2025, 4:36pm UTC](https://forums.percona.com/t/error-setup-failed-to-register-multicluster-service-error-get-api-groups-and-resources/39048 "2025-08-09T16:36:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Seshan\_Kannan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/seshan_kannan/32/21747_2.png) [@Seshan\_Kannan](https://forums.percona.com/u/Seshan_Kannan)\
**Post date:** [August 9, 2025, 4:36pm UTC](https://forums.percona.com/t/error-setup-failed-to-register-multicluster-service-error-get-api-groups-and-resources/39048/1 "2025-08-09T16:36:34Z")

</div>

Dear team,  
Need your help in resolving the following issue. The operator instance fails to come up with the following error.

```auto
[seshankannan@kubectl-instance ~]$ kubectl logs -n default deployment/percona-operator-psmdb-operator --tail=200 -f

2025-08-09T16:19:03.878Z INFO setup Manager starting up {“gitCommit”: “30d9ec941baf57619c8973249a3c5d3fd5cc08f4”, “gitBranch”: “release-1-20-1”, “buildTime”: “”, “goVersion”: “go1.24.3”, “os”: “linux”, “arch”: “amd64”}

2025-08-09T16:19:03.911Z ERROR setup failed to register multicluster service {“error”: “get api groups and resources: unable to retrieve the complete list of server APIs: custom.metrics.k8s .io/v1: stale GroupVersion discovery: custom.metrics.k8s.io/v1, tap.linkerd.io/v1alpha1: stale GroupVersion discovery: tap.linkerd. io/v1alpha1”, “errorVerbose”: “unable to retrieve the complete list of server APIs: custom.metrics.k8s. io/v1: stale GroupVersion discovery: custom.metrics.k8s. io/v1, tap.linkerd. io/v1alpha1: stale GroupVersion discovery: tap.linkerd. io/v1alpha1\nget api groups and resources\ngithub.com/percona/percona-server-mongodb-operator/pkg/mcs.Register\n\t/go/src/github.com/percona/percona-server-mongodb-operator/pkg/mcs/register.go:39\nmain.main\n\t/go/src/github.com/percona/percona-server-mongodb-operator/cmd/manager/main.go:133\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:283\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1700”}

main.main

/go/src/github.com/percona/percona-server-mongodb-operator/cmd/manager/main.go:134

runtime.main

/usr/local/go/src/runtime/proc.go:283

```

Also, assuming that this is happening due to multicluster support, how can we disable it? I did some customization to the chart to enforce it by making the following change.  
env:

```auto
name: LOG_STRUCTUREDvalue: “{{ .Values.logStructured }}”

name: LOG_LEVELvalue: “{{ .Values.logLevel }}”

name: WATCH_NAMESPACE{{- if .Values.watchAllNamespaces }}value: “”{{- else }}value: “{{ default .Release.Namespace .Values.watchNamespace }}”{{- end }}

name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.name

name: OPERATOR_NAMEvalue: “{{ default “percona-server-mongodb-operator” .Values.operatorName }}”

name: RESYNC_PERIODvalue: “{{ .Values.env.resyncPeriod }}”

name: DISABLE_TELEMETRYvalue: “{{ .Values.disableTelemetry }}”

name: MCS_ENABLED # added thisvalue: “false”

```

And also added the following to my operator deployment yaml.

```auto
mcs:enabled: false

```

I need your help in finding a solution to this. Critical to what we are planning to setup at our workplace. Appreciate any support in resolving this.

Thanks in advance,  
Seshan K.