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

unscheduing pod #13

Open
tae2089 opened this issue May 21, 2024 · 1 comment
Open

unscheduing pod #13

tae2089 opened this issue May 21, 2024 · 1 comment
Assignees

Comments

@tae2089
Copy link
Member

tae2089 commented May 21, 2024

Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  kube-api-access-n2l2v:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age   From               Message
  ----     ------            ----  ----               -------
  Warning  FailedScheduling  25s   default-scheduler  0/1 nodes are available: 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
@tae2089 tae2089 self-assigned this May 21, 2024
@tae2089
Copy link
Member Author

tae2089 commented May 21, 2024

유빈님이 해줄 예정
문제는 affinity 설정으로 인해서 배치가 안됨

@yubin1010 yubin1010 self-assigned this May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants