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
{{ message }}
This repository has been archived by the owner on Nov 22, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
Cloudflow deployments do not provide the ability to schedule pods on specific nodes in k8s cluster.
Is your feature request related to a specific runtime of cloudflow or applicable for all runtimes?
This is relevant for all runtimes deployment to k8s.
Describe the solution you'd like
Currently, we can declare k8s related configuration in a conf file and provide as --conf to kubectl cloudflow. However, these configuration do not support tolerations for pods that can be scheduled on nodes with matching taints in the k8s cluster.
Therefore, it is highly recommended to make this feature available in the cloudflow operator to parse this and add to the deployments before deploying them in the cluster.
Is your feature request related to a problem? Please describe.
Cloudflow deployments do not provide the ability to schedule pods on specific nodes in k8s cluster.
Is your feature request related to a specific runtime of cloudflow or applicable for all runtimes?
This is relevant for all runtimes deployment to k8s.
Describe the solution you'd like
Currently, we can declare k8s related configuration in a
conf
file and provide as--conf
tokubectl cloudflow
. However, these configuration do not supporttolerations
for pods that can be scheduled on nodes with matchingtaints
in thek8s
cluster.Therefore, it is highly recommended to make this feature available in the
cloudflow
operator to parse this and add to the deployments beforedeploying
them in the cluster.Describe alternatives you've considered
N/A
Additional context
For details on
taints
andtolerations
- see https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/The text was updated successfully, but these errors were encountered: