Ingress enricher merges opinionated defaults with provided Fragments

[manusa]

Description

The Ingress enricher is only used for Ingress creation purposes.

Scenarios such as the following are not covered:

• Fragment provided for extensions/v1beta1
  • 2.1 Generate and merge ingress with apiVersion networking.k8s.io/v1
  • 2.2 Generate and merge ingress with apiVersion extensions/v1beta1
• Fragment provided for networking.k8s.io/v1
  • 3.1 Generate and merge ingress with apiVersion networking.k8s.io/v1 (-Djkube.enricher.jkube-ingress.targetApiVersion='networking.k8s.io/v1') ❌
  • 3.2 Generate and merge ingress with apiVersion extensions/v1beta1

This feature might be interesting for users who target different Kubernetes clusters and might want to generate different resources Ingress APIs but provide a single Fragment.

Currently the Ingress Enricher only generates the opinionated Ingress in case there's no Ingress fragment with a matching name. For this cases, it might be interesting to convert the Ingress to the desired target version in case is set.

Another pending question is if we want to merge opinionated defaults with missing information in the provided fragments.

Relates to

• Add configuration options to IngressEnricher #551
• Fix #551: Add Configuration options to IngressEnricher #723

[manusa]

It might be worth considering the Deployment approach and provide specific enrichers to perform the merge.