-
Notifications
You must be signed in to change notification settings - Fork 871
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
fix: scheduler/descheduler installed failed by operator #5519
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: zhzhuang-zju <m17799853869@163.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5519 +/- ##
==========================================
- Coverage 32.45% 32.45% -0.01%
==========================================
Files 643 643
Lines 44497 44499 +2
==========================================
Hits 14442 14442
- Misses 28961 28962 +1
- Partials 1094 1095 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
test report: # karmada.yaml
apiVersion: operator.karmada.io/v1alpha1
kind: Karmada
metadata:
name: karmada-demo
namespace: test
spec:
crdTarball:
httpSource:
url: https://github.com/karmada-io/karmada/releases/download/v1.11.0/crds.tar.gz
components:
etcd:
local:
imageRepository: registry.k8s.io/etcd
imageTag: 3.5.13-0
replicas: 1
volumeData:
# hostPath:
# type: DirectoryOrCreate
# path: /var/lib/karmada/etcd/karmada-demo
volumeClaim:
metadata:
name: etcd-data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 3Gi
karmadaAPIServer:
imageRepository: registry.k8s.io/kube-apiserver
imageTag: v1.29.6
replicas: 1
serviceType: NodePort
serviceSubnet: 10.96.0.0/12
karmadaAggregatedAPIServer:
imageRepository: docker.io/karmada/karmada-aggregated-apiserver
imageTag: v1.11.0
replicas: 1
karmadaControllerManager:
imageRepository: docker.io/karmada/karmada-controller-manager
imageTag: v1.11.0
replicas: 1
karmadaScheduler:
imageRepository: docker.io/karmada/karmada-scheduler
imageTag: v1.11.0
replicas: 1
karmadaWebhook:
imageRepository: docker.io/karmada/karmada-webhook
imageTag: v1.11.0
replicas: 1
kubeControllerManager:
imageRepository: registry.k8s.io/kube-controller-manager
imageTag: v1.29.6
replicas: 1
karmadaMetricsAdapter:
imageRepository: docker.io/karmada/karmada-metrics-adapter
imageTag: v1.11.0
replicas: 2
# karmadaSearch: # the component `Karmadasearch` is not installed by default, if you need to install it, uncomment it and note the formatting
# imageRepository: docker.io/karmada/karmada-search
# imageTag: v1.8.0
# replicas: 1
karmadaDescheduler: # the component `KarmadaDescheduler` is not installed by default, if you need to install it, uncomment it and note the formatting
imageRepository: docker.io/karmada/karmada-descheduler
imageTag: v1.11.0
replicas: 1
hostCluster:
networking:
dnsDomain: cluster.local
|
cc @chaosi-zju |
seems to be accidentally introduced in #5040 /lgtm |
/assign @RainbowMango |
@zhzhuang-zju How to reproduce it? Does #5040 introduce this issue? |
Yes, Just follow the steps as described in comments #5519 (comment) and will reproduce this issue. I think we can add a CI for installation by the |
Recently, karmada-operator has added many new features. The installation verification in #4401 might not be sufficient anymore. For example, it does not validate the installation of the component |
OK, please cc me again #4401 once it's ready. By the way, I think this PR can help update https://github.com/karmada-io/karmada/blob/master/operator/config/samples/karmada.yaml, so that the bugs can be found more easily. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
karmada/operator/pkg/controlplane/controlplane.go
Lines 141 to 154 in 07e2976
Argument
{{ .KarmadaCertsSecret }}
inscheduler/descheduler's manifest
also need to be parsedWhich issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
BTW, I think we chould push for the integration of #4401 to establish a code merge gate for the karmada-operator.
Does this PR introduce a user-facing change?: