Rethink Route/Ingress generation

[rhuss]

Description

Currently the configuration and generation of a Route/Ingress via automatic enrichment is a bit interwoven. For the target goal, to move all central logic into Maven independent parts (like enrichers), an option like fabric8.openshift.generateRoute=false which just filters out any routes during writing of the resource files, is problematic as a user might explicit´ly configure a route e.g. via a fragment might lead to conflicting situations.

Actually, every postprocessing of the generated resource files (like it happens also for converting Kubernetes to OpenShift objects) conflicts the way how the enrichment process is intended.

Ideally everything happens in the enrichers. So a good solution would be to move everything into RouteIngressEnricher and just disable this enricher if you don't want a route or ingress (which can be easily done with a profile, too).

Another issue with the current RouteEnricher is that it depends on the ExposeEnricher that a certain label gets added to a service which is picked up by the route enricher. Instead, the RouteEnricher should examine itself all service and should be able to configure to select the service to expose. This is much easier to understand, and makes the ExposeEnricher obsolete.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!