Skip to content

Removes modelmesh-enabled label#291

Open
QuanMPhm wants to merge 1 commit intonerc-project:mainfrom
QuanMPhm:ops_1017/model_serve
Open

Removes modelmesh-enabled label#291
QuanMPhm wants to merge 1 commit intonerc-project:mainfrom
QuanMPhm:ops_1017/model_serve

Conversation

@QuanMPhm
Copy link
Contributor

Closes nerc-project/operations#1017

The default Openshift label modelmesh-enabled has been removed. This label prevents the user from choosing the model-serving option in their RHOAI namespace, which is the desired user behavior.

More details in the linked issue being closed

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Removes the modelmesh-enabled OpenShift namespace label from this plugin’s default namespace labels to avoid forcing a specific model-serving configuration in RHOAI namespaces.

Changes:

  • Removed modelmesh-enabled: "true" from PROJECT_DEFAULT_LABELS.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 31 to 35
PROJECT_DEFAULT_LABELS = {
"opendatahub.io/dashboard": "true",
"modelmesh-enabled": "true",
"nerc.mghpcc.org/allow-unencrypted-routes": "true",
"nerc.mghpcc.org/project": "true",
}
Copy link

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing modelmesh-enabled from PROJECT_DEFAULT_LABELS prevents it from being added to new namespaces, but existing namespaces will keep the label because validate_allocations' sync_openshift_project_labels only adds missing labels and never removes labels that are no longer defaults. If the goal is to unblock model-serving selection for existing RHOAI namespaces too, consider explicitly deleting modelmesh-enabled during validation/migration when --apply is used (without removing other user-managed labels).

Copilot uses AI. Check for mistakes.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@IsaiahStapleton do you want modelmesh-enabled: True to be removed from all existing namespaces?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Milstein What do you think? I think no, because the user can already change it themselves so it might be disruptive to change all of them now like that.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@IsaiahStapleton so you just want the label to not be added for new namespaces going forward?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@knikolla I think that's what would be best yes. Not sure what others think.

Copy link
Collaborator

@knikolla knikolla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me pending confirmation from @Milstein and @jtriley that they don't want the label removed from existing allocations, but only not added to new ones.

The default Openshift label `modelmesh-enabled` has been removed.
This label prevents the user from choosing the model-serving
option in their namespace, which is the desired user behavior.

More details here: nerc-project/operations#1017
@QuanMPhm QuanMPhm force-pushed the ops_1017/model_serve branch from 8e923fc to 8cbdd29 Compare February 13, 2026 16:47
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

Successfully merging this pull request may close these issues.

Fix issue of Coldfront automatically assigning multi model serving for new project namespaces in RHOAI

3 participants