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 Aug 17, 2023. It is now read-only.
Currently, via #123 , a control-plane label is applied to namespaces where kubeflow is running. While this is well-intentioned (to prevent the application of kubeflow webhooks), it unfortunately causes collisions with other solutions.
This issue is a request for enhancement to make the key (control-plane) configurable.
An alternate suggestion would be to make the fixed key prefixed in some way. eg: kf-control-plane.
At this time, the control-plane label is causing an issue with knative serving deployments (no issue has been filed for that yet).
The text was updated successfully, but these errors were encountered:
Upvoting it.
In Azure that label also blocks Istio Injection for Kubeflow namespace because of Azure/AKS#1771
Whenever I use kfctl to apply some changes I need to remove the control-plane label from Kubeflow namespace and rollout restart all the deployments.
Currently, via #123 , a
control-plane
label is applied to namespaces where kubeflow is running. While this is well-intentioned (to prevent the application of kubeflow webhooks), it unfortunately causes collisions with other solutions.This issue is a request for enhancement to make the key (
control-plane
) configurable.An alternate suggestion would be to make the fixed key prefixed in some way. eg:
kf-control-plane
.At this time, the
control-plane
label is causing an issue with knative serving deployments (no issue has been filed for that yet).The text was updated successfully, but these errors were encountered: