Document listenerClass usage in operators or global concepts page

[maltesander]

We currently do not document properly how our services are created.

After stackabletech/issues#360 we do not create NodePorts per default, this changes the way users interacted with our products (you explicitly have to set the listenerClass if you want a NodePort).

This should be fixed in each operator, or a global concepts page should be created and linked to in each operator.

• global concepts page updated: Updated text for service exposition #446

Tasks

Beta Give feedback

1. Add docs for listenerClass in each operator
2. Fix comment in CRD to proper english
3. Adapt getting started guides and (if available) examples with listenerClass Nodeports

Operators

Beta Give feedback

1. Service exposition docs airflow-operator#320
   0 of 11
   +0
2. ListenerClass docs druid-operator#466
   0 of 11
   +0
3. ListenerClass docs hbase-operator#390
   0 of 11
   +0
4. ListenerClass docs hdfs-operator#387
   0 of 11
   +0
5. ListenerClass docs hive-operator#367
   0 of 11
   +0
6. Kafka -> Not configurable, only nodePort supported
7. ListenerClass docs opa-operator#471
   0 of 11
   +0
8. ListenerClass docs nifi-operator#500
   0 of 11
   +0
9. ListenerClass docs spark-k8s-operator#276
   0 of 11
   +0
10. ListenerClass docs superset-operator#399
    4 of 11
    +0
11. ListenerClass docs trino-operator#465
    0 of 11
    +0
12. Add ListenerClass docs zookeeper-operator#721
    0 of 11
    +0

[lfrancke]

While we're at it we should look at the CRD level docs for the listenerClass as well as that doesn't seem to be entirely proper english.

[maltesander]

We should add the listenerClass: external-unstable in all getting started guides and examples as well. Otherwise you might install it but are not able to interact with the UI.

[lfrancke]

Maybe already done: https://docs.stackable.tech/home/stable/concepts/service-exposition.html
Check during refinement

[lfrancke]

Can this issue be closed?

[fhennig]

damnit! Yes, forgot it again ..