ODO and other tools should recognize managed services without knowing exact names of CRDs

[wtrocki]

Managed Kafka Connection needs to be recognized in ODO. This will not happen now as services are needed to be backed by deployment.

We need to start using annotations for Managed (Kafka) Connection objects.

[pmuir]

https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/#attaching-metadata-to-objects

Probably labels are useful as this is something you might want to select on.

[wtrocki]

@secondsun I will create follow up issue to add support to ODO but I think we should attach labels now - this is not breaking change but having some labels under discussion will enable us to group them for multiservice environment.

Done some reading and there is no need to add new elements. Acording to
https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels

we can use:

app.kubernetes.io/component="external-service"
app.kubernetes.io/managed-by="rhoas"

not sure about external-service - naming are hot area but I think this is clear for everyone

[secondsun]

ODO ? https://memory-alpha.fandom.com/wiki/Odo or https://docs.openshift.com/container-platform/4.7/cli_reference/developer_cli_odo/understanding-odo.html

[pmuir]

https://odo.dev/

[wtrocki]

ODO ? memory-alpha.fandom.com/wiki/Odo

😆

[secondsun]

What does the perceived odo workflow look like, and where would we need to integrate with it? I am imagining a cluster with firepig installed and you odo make a java project then odo add mkc (yes I know these aren't odo commands, but pretend they are). odo will then make sure that the MKC values are injected into your java project/pod/deployment.

Is this an alternative to the service binding operator, or do they work hand in hand? is the target audience of odo people who are REALLY scared of yaml files?

[wtrocki]

ODO just needs to recognize MKC as service. It does by having CR that.. has deployment.
Our case doesn't have deployment so we need to somehow teach odo that MKC MSRC etc. are the resources you can created binding for.

On the low level we can create binding between anything so there is no such limitation.

[wtrocki]

Started discussion on the ODO issue. I Will also mention this on the Friday call:

redhat-developer/odo#4236

[wtrocki]

@secondsun I had some discussions about this and generally we should add labels:

app.kubernetes.io/component="external-service"
app.kubernetes.io/managed-by="rhoas"

No other action is needed for this issue.
Let's add those (I will not do it since you are assigned to that already)

[secondsun]

All right, will do!

[secondsun]

After doing some more research, I don't think the operator is the place were labels should be added. Labels should be applied when the crs are created either by the CLI or the BFF. I'll update the examples in the operator directory.

[wtrocki]

Leaving that for the time when we have extra service. There are couple strategies for grouping

[wtrocki]

Recomendation was done to use groups for supported resources etc.
Closing as there will be no action for this needed.