DaoCloud / karmada-operator1

DaoCloud/karmada-operator1 Issues

karmada chart offline installtion
Updated 2 years ago
upgrade karmada version to v1.3.0
Updated 2 years ago
karmada controller always CrashLoopBackOff
Updated 2 years ago
karmada operator retry mechanism
Updated 2 years ago1
cannot delete namespace of karmada when delete kmd CR
Updated 2 years ago1
how to upgrade karmada instance
Updated 2 years ago
the `workflowSummary` ready number is alway to zero
Updated 2 years ago
supprot karmada operator images mutils arch build
Updated 2 years ago
generate a non-conflicting namespace for the karmada instance
Closed 2 years ago1
add ci workflow to push operator image and chart to registry
Updated 2 years ago
support set registry for other images example `postInstallJob` or `preInstallJob`
Closed 2 years ago2
we need a e2e test to ensure that the Controller works properly
Updated 2 years ago
whether to delete etcd data when deleting Karmada instance
Updated 2 years ago
structured logging: we need normative log output
Closed 2 years ago1
When installing the second karmada instance, an error port conflict is reported
Closed 2 years ago1
gather overview information of the member cluster to karmadaDeployment
Closed 2 years ago1
use ghcr image repo instead of release.daocloud.io
Closed 2 years ago1
Unable to use sample to create karmada
Closed 2 years ago
The karmada instance installation process needs a clearer condition to describe the LCM progress
Closed 2 years ago1
Provides a configuration parameter that allows karmada instances to remain when the CR is deleted
Closed 2 years ago3
about ETCD spec
Updated 2 years ago1