-
Notifications
You must be signed in to change notification settings - Fork 68
HOLD: add label to NS #285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Ryan Cook <[email protected]>
WalkthroughAdded a new string label modelmesh-enabled: 'false' under metadata.labels to the Kubernetes Namespace manifest at kubernetes/namespace/namespace.yaml. All other fields remain unchanged. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Nitpick comments (1)
kubernetes/namespace/namespace.yaml (1)
7-8: Confirm intended semantics for modelmesh-enabled label valueDouble-check that setting modelmesh-enabled to "false" is the intended behavior for your RHOAI/ModelMesh integration. Some controllers look for "true" to enable behavior and ignore or default otherwise. Please verify the expected effect in your environment before merging.
I can help adjust this manifest or add a Kustomize patch across environments once you confirm the desired behavior.
| labels: | ||
| modelmesh-enabled: 'false' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix: labels are incorrectly nested under annotations; move to metadata.labels
In Kubernetes, metadata.annotations values must be strings, and labels must be a sibling of annotations under metadata. As written, this will fail validation (annotations contains an object-valued key "labels"). Place labels directly under metadata.
Apply this diff to correct the structure:
metadata:
name: llama-serve
- annotations:
- argocd.argoproj.io/sync-wave: "0"
- labels:
- modelmesh-enabled: 'false'
+ labels:
+ modelmesh-enabled: "false"
+ annotations:
+ argocd.argoproj.io/sync-wave: "0"📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| labels: | |
| modelmesh-enabled: 'false' | |
| metadata: | |
| name: llama-serve | |
| labels: | |
| modelmesh-enabled: "false" | |
| annotations: | |
| argocd.argoproj.io/sync-wave: "0" |
🤖 Prompt for AI Agents
In kubernetes/namespace/namespace.yaml around lines 7 to 8, the labels block is
mistakenly placed under metadata.annotations (creating an object-valued
annotation) which breaks validation; move the labels map out of annotations and
place it as a sibling under metadata.labels with string values (e.g.,
modelmesh-enabled: "false"), removing the labels key from annotations so
annotations contains only string key:value pairs.
Add label to namespace for better RHOAI experience.
HOLD until I can test
Summary by CodeRabbit