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
When CreateUpdatePodForSchedulingHandler Handle pod, should treats pod without Label fluid.io/enable-injection same as pod with fluid.io/enable-injection=false,just skip mutating the pod
Why is this feature needed:
In the k8s clusters of many companies, there are many other services that do not require fluid.
If CreateUpdatePodForSchedulingHandler could treats pod without Label fluid.io/enable-injection same as pod with Labelfluid.io/enable-injection=false, these services could continue work without the need for additional modifications that add labels fluid.io/enable-injection=false to the pod of services
The text was updated successfully, but these errors were encountered:
@kingeasternsun Thanks for the issue. Which version of Fluid are you using? We have now turned to use objectSelector instead of the namespaceSelector``fluid.io/enable-injection. You can trigger webhook mutations at pod-level with pod.metadata.labels={"fuse.serverful.fluid.io/inject": "true"} or pod.metadata.labels={"serverless.fluid.io/inject": "true"}. Please see here and here for detailed examples.
What feature you'd like to add:
When
CreateUpdatePodForSchedulingHandler
Handle pod, should treats pod without Labelfluid.io/enable-injection
same as pod withfluid.io/enable-injection=false
,just skip mutating the podWhy is this feature needed:
In the k8s clusters of many companies, there are many other services that do not require fluid.
If
CreateUpdatePodForSchedulingHandler
could treats pod without Labelfluid.io/enable-injection
same as pod with Labelfluid.io/enable-injection=false
, these services could continue work without the need for additional modifications that add labelsfluid.io/enable-injection=false
to the pod of servicesThe text was updated successfully, but these errors were encountered: