Skip to content

Install to namespaces other than karmada-system via helm chart. #6580

@tsuijie

Description

@tsuijie

hi @levkp, can you try install karmada at karmada-system namespace? (do not use other namespace)

Originally posted by @chaosi-zju in #4942

Hi, install karmada via helm chart to namespace other than karmada-system will cause karmada controller crash.

  1. karmada-controller-manager

controllermanager.go:221] controller manager exits unexpectedly: failed to wait for unified-auth-controller caches to sync kind source: *v1alpha1.Cluster: timed out waiting for cache to be synced for Kind *v1alpha1.Cluster

  1. karmada-apiserver

controller.go:116] loading OpenAPI spec for "v1alpha1.cluster.karmada.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: error trying to reach service: tls: failed to verify certificate: x509: certificate is valid for kubernetes.default.svc, *.etcd.karmada-2.svc.cluster.local, *.karmada-2.svc.cluster.local, *.karmada-2.svc, localhost, not karmada-aggregated-apiserver.karmada-system.svc

Looks like karmada apiserver forgot to change aggregated-apiserver api namespace.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions