A nitpick and not that important --- are we comfortable to have `opendatahub.io` in the rhds repo; could it be misleading eventually? probably we don't need to care, just thinking outloud.

[jiridanek]

A nitpick and not that important --- are we comfortable to have opendatahub.io in the rhds repo; could it be misleading eventually? probably we don't need to care, just thinking outloud.

Originally posted by @jstourac in #570 (comment)

[jiridanek]

kubeflow/components/base/README.md

Line 47 in c03da1a

notebooks.opendatahub.io/inject-oauth: "true"

[jiridanek]

kubeflow/components/odh-notebook-controller/controllers/notebook_controller.go

Lines 50 to 55 in c03da1a

	const (
	AnnotationInjectOAuth = "notebooks.opendatahub.io/inject-oauth"
	AnnotationServiceMesh = "opendatahub.io/service-mesh"
	AnnotationValueReconciliationLock = "odh-notebook-controller-lock"
	AnnotationLogoutUrl = "notebooks.opendatahub.io/oauth-logout-url"
	)

[jiridanek]

kubeflow/components/odh-notebook-controller/controllers/opentelemetry_test.go

Line 81 in c03da1a

const name = "opendatahub.io/kubeflow/components/odh-notebook-controller/controllers/opentelemetry_test.go"

[jiridanek]

@jstourac yeah, I think we need not care, we already have tons of opendatahub.io around already, and there's really nothing we can do