-
Notifications
You must be signed in to change notification settings - Fork 67
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
Update base MR service to include labels and annotations for the BFF #525
Update base MR service to include labels and annotations for the BFF #525
Conversation
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.
Looks good to me, but let's wait for other chime in before merge.
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.
/lgtm
Let's wait on @tarilabs just to confirm.
@lucferbux: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
app: metadata | ||
component: model-registry |
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.
My suggestion is to seize this chance to align label app and component in the Service here as:
app: metadata | |
component: model-registry | |
app: model-registry | |
component: model-registry-server |
to be consistent with the Deployment:
kind: Deployment | |
metadata: | |
name: model-registry-deployment | |
labels: | |
component: model-registry-server |
@Al-Pragliola @isinyaaa @dhirajsb wdyt ?
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.
The app name is used to group related resources in a single app. E.g. the MR itself, it's deployment, service, istio resources, etc. should all use the same app name.
So, we set it to the MR name downstream. The downstream labels are:
labels:
app: modelregistry-sample
app.kubernetes.io/component: model-registry
app.kubernetes.io/created-by: model-registry-operator
app.kubernetes.io/instance: modelregistry-sample
app.kubernetes.io/managed-by: model-registry-operator
app.kubernetes.io/name: modelregistry-sample
app.kubernetes.io/part-of: model-registry
component: model-registry
name: modelregistry-sample
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.
So I should add all of these labels?
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.
@Al-Pragliola can you take up the task of consolidating the useful ones from here into a replacements yaml for an MR template for overlays?
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.
@Griffin-Sullivan we can start with app
, and component
labels, we can definitely skip the operator label values as they don't apply.
We should use app.kubernetes.io labels to be consistent with k8s recommendations.
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.
@dhirajsb let me know what you think I added the changes.
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.
lgtm @Griffin-Sullivan
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.
Let's keep the service name the same. The sample I shared was to show the label names as an example, not the label values for kubeflow manifests.
displayName: Default Model Registry | ||
description: The default model registry |
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.
displayName: Default Model Registry | |
description: The default model registry | |
displayName: Kubeflow Model Registry | |
description: An example model registry |
b89e628
to
d35b934
Compare
@lucferbux: changing LGTM is restricted to collaborators In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
it looks to me #525 (comment) is not yet addressed. |
d35b934
to
a846a62
Compare
/lgtm |
@dhirajsb: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@@ -2,8 +2,16 @@ kind: Service | |||
apiVersion: v1 | |||
metadata: | |||
labels: | |||
app: metadata | |||
name: model-registry-service | |||
app: modelregistry-sample |
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.
app: modelregistry-sample | |
app: model-registry-service |
name: model-registry-service | ||
app: modelregistry-sample | ||
app.kubernetes.io/component: model-registry | ||
app.kubernetes.io/instance: modelregistry-sample |
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.
app.kubernetes.io/instance: modelregistry-sample | |
app.kubernetes.io/instance: model-registry-service |
app: modelregistry-sample | ||
app.kubernetes.io/component: model-registry | ||
app.kubernetes.io/instance: modelregistry-sample | ||
app.kubernetes.io/name: modelregistry-sample |
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.
app.kubernetes.io/name: modelregistry-sample | |
app.kubernetes.io/name: model-registry-service |
annotations: | ||
displayName: Kubeflow Model Registry | ||
description: An example model registry | ||
name: modelregistry-sample |
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.
name: modelregistry-sample | |
name: model-registry-service |
Signed-off-by: Griffin-Sullivan <gsulliva@redhat.com>
a846a62
to
e87f6f4
Compare
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.
/lgtm
@dhirajsb: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dhirajsb, ederign, lucferbux, tarilabs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
Adding a new label called
component
and setting it tomodel-registry
. This will allow us to filter services in the BFF rather than looping through all services.Also adding annotations for
displayName
anddescription
. The BFF looks for these annotations to display the name of the MR when changing registries in the UI. Everything will work without these but this is a nicer UX and can help with determining which model registry is which.How Has This Been Tested?
Tested locally on kind and got:
Merge criteria:
DCO
check)If you have UI changes