Skip to content
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

When using reclaim core pod, the pod cannot be scheduled #331

Open
Lan-ce-lot opened this issue Oct 25, 2023 · 0 comments
Open

When using reclaim core pod, the pod cannot be scheduled #331

Lan-ce-lot opened this issue Oct 25, 2023 · 0 comments
Assignees
Labels

Comments

@Lan-ce-lot
Copy link
Contributor

What happened?

image

reclaimed-normal-pod.yaml

apiVersion: v1
kind: Pod
metadata:
  annotations:
    "katalyst.kubewharf.io/qos_level": reclaimed_cores
  name: reclaimed-normal-pod
  namespace: default
spec:
  containers:
    - name: stress
      image: joedval/stress:latest
      command:
        - stress
        - -c
        - "1"
      imagePullPolicy: IfNotPresent
      resources:
        requests:
          "resource.katalyst.kubewharf.io/reclaimed_millicpu": "2k"
          "resource.katalyst.kubewharf.io/reclaimed_memory": 1Gi
        limits:
          "resource.katalyst.kubewharf.io/reclaimed_millicpu": "2k"
          "resource.katalyst.kubewharf.io/reclaimed_memory": 1Gi
  schedulerName: katalyst-scheduler

What did you expect to happen?

Reclaim core pod completes scheduling.

How can we reproduce it (as minimally and precisely as possible)?

Use the default policy scheduler-policy-spread.yaml of the example folder.

Software version

$ <software> version
# paste output here
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants