You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There is a toleration issue related to job scheduling in the Kubernetes cluster. The job is expected to tolerate specific taints on the nodes, but it fails to do so, leading to scheduling problems and the job being stuck in a pending state.
To Reproduce
Steps to reproduce the behavior:
Deploy the job with the specified toleration in the YAML file.
Apply the job configuration to the Kubernetes cluster.
Check the status of the job using kubectl get jobs.
Observe that the job remains in a pending state due to node taints.
Expected behavior
The job should tolerate the taints specified in its configuration and be scheduled on the appropriate node, moving from pending to running state.
Screenshots
If applicable, add screenshots to help explain your problem. (E.g., screenshots of the YAML configuration and the job's status in the Kubernetes dashboard.)
Desktop (please complete the following information):
OS: [e.g. Ubuntu 20.04]
Browser [e.g. Chrome, Firefox]
Version [e.g. Chrome 93]
Smartphone (please complete the following information):
Device: [e.g. OnePlus 7T]
OS: [e.g. Android 11]
Browser [e.g. Chrome, Firefox]
Version [e.g. Chrome 93]
Additional context
This issue may be related to the configuration of the taints and tolerations in the job's YAML file. Please verify that the taint keys and values match exactly with the node's taints.
The text was updated successfully, but these errors were encountered:
classDiskBenchmarkParams(PodRunningParams):
""" :var pvc_name: Name of the pvc created for the benchmark. :var test_seconds: The benchmark duration. :var namespace: Namespace used for the benchmark. :var disk_size: The size of pvc used for the benchmark. :var storage_class_name: Pvc storage class, From the available cluster storage classes. standard/fast/etc. """pvc_name: str="robusta-disk-benchmark"test_seconds: int=20namespace: str=INSTALLATION_NAMESPACEdisk_size: str="10Gi"storage_class_name: str
Describe the bug
There is a toleration issue related to job scheduling in the Kubernetes cluster. The job is expected to tolerate specific taints on the nodes, but it fails to do so, leading to scheduling problems and the job being stuck in a pending state.
To Reproduce
Steps to reproduce the behavior:
kubectl get jobs
.Expected behavior
The job should tolerate the taints specified in its configuration and be scheduled on the appropriate node, moving from pending to running state.
Screenshots
If applicable, add screenshots to help explain your problem. (E.g., screenshots of the YAML configuration and the job's status in the Kubernetes dashboard.)
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
This issue may be related to the configuration of the taints and tolerations in the job's YAML file. Please verify that the taint keys and values match exactly with the node's taints.
The text was updated successfully, but these errors were encountered: